Meta Catalog

Meta Catalog

This connector reads and maintains Meta product catalogs (Commerce Manager) through the Graph API (https://graph.facebook.com/v26.0): the catalogs of a business portfolio and those shared by clients, products with their review status and errors, product sets, data feeds with their uploads and upload errors, and catalog diagnostics. Writes (batch updates, creating, changing and deleting single products) are installed switched off. Catalogs feed Advantage+ catalog ads, Facebook and Instagram Shops and product tagging, so a change here shows up there.

Setup (about 10 minutes)

1. Open https://developers.facebook.com/apps/creation/ and create a business app connected to your business portfolio (or reuse the app of the Meta Ads connector).
2. Recommended, a token that does not expire: in Business Settings (https://business.facebook.com/settings) open Users → System users, add a system user, then Assign assets → Catalogs → your catalog (Manage catalog, or View catalog for read-only). Click Generate token, pick the app, choose Never as expiry and tick catalog_management and business_management. Meta can ask you to verify the business portfolio before a system user may generate a token.
3. Alternative, a user token: the Graph API Explorer (https://developers.facebook.com/tools/explorer/), your app, User Token with the same two permissions. That token lasts one or two hours. Set META_APP_ID and META_APP_SECRET (the app's App settings, Basic) and AnythingMCP exchanges it for a long-lived token (about 60 days) on its first call and renews it once fewer than 10 days remain. Without them, extend it yourself in the Access Token Debugger (https://developers.facebook.com/tools/debug/accesstoken, Extend Access Token) and replace it before the 60 days run out; the connector page warns ahead of time.
4. Paste the token into META_CATALOG_ACCESS_TOKEN and the business portfolio id into META_CATALOG_BUSINESS_ID (Business Settings → Business info, or the business_id= in the address bar of business.facebook.com). meta_catalog_list_businesses lists them for a user token; for a system user token it usually returns an empty list, so take the id from Business Settings.
5. Install, then run meta_catalog_check_permissions and meta_catalog_list_catalogs.

Which tool first: meta_catalog_list_catalogs (or meta_catalog_list_client_catalogs for catalogs a client shared) gives the catalog_id; then meta_catalog_list_products, meta_catalog_list_product_sets, meta_catalog_list_feeds and meta_catalog_get_diagnostics take it. For "why are my products rejected or not showing": meta_catalog_get_diagnostics, then meta_catalog_list_products with error_priority HIGH or a filter on review_status, then meta_catalog_get_product (fields errors, review_rejection_reasons). For feed problems: meta_catalog_list_feeds → meta_catalog_list_feed_uploads → meta_catalog_list_upload_errors.

Ids: a product has a Meta id (used by meta_catalog_get_product, meta_catalog_update_product, meta_catalog_delete_product) and your own retailer_id (the SKU, the id column of a feed, used in batch requests and filters). Ids are long numbers: pass them as strings.

Lists and fields: lists return data[] and paging.cursors.after; pass it as after for the next page (no paging.next means the last page). Each tool returns only the fields in fields (each has a useful default). filter takes a JSON rule such as {"retailer_id":{"is_any":["sku1","sku2"]}}, {"availability":{"eq":"out of stock"}} or {"and":[{"price":{"gt":5000}},{"brand":{"i_contains":"acme"}}]}; summary=total_count adds the number of matching products.

Money: when reading, price and sale_price are strings with the currency (19.99 EUR). When creating or updating a single product, price is an integer in the minor unit (1999 = 19.99) with currency. In batch requests prices are strings with the currency ("19.99 EUR"), and the data uses feed field names (id = retailer_id, title, link, image_link).

Changes reach ads and shops: confirm first. The write tools are switched off at install; turn them on per tool if the AI should edit the catalog. Before any write, state the catalog, the items (name and retailer_id) and the old and new values, and wait for the user's yes. meta_catalog_batch_update_items is asynchronous: follow its handle with meta_catalog_check_batch_status until finished, then report the errors. Items that a scheduled feed supplies are overwritten by the next feed upload, so for lasting changes fix the feed source (or use a supplementary feed).

Instagram: tagging products in posts and publishing are not part of this connector; the Instagram connector covers Instagram publishing, comments and insights.

Common errors (in error.code)

• 190: the token is invalid or expired; create a new one. With subcode 467 (logged out), 460 (password changed) or 458 (app removed) the session is over for good: the connector stops sending the token and answers at once until a new one is saved.
• 10, 200 to 299: a permission is missing (catalog_management, business_management) or the system user has no access to this catalog. Assign the catalog to the system user and generate the token again.
• 100: a parameter, field or filter is wrong; error.message names it. A filter must be valid JSON.
• 4, 17, 613, 80009, 80014: rate limits (80014 is the batch limit); wait a few minutes.

Out of scope here: creating or deleting catalogs, feeds and product sets, feed schedules and file uploads, localized catalogs and overrides, pixels and event sources, and catalog ads themselves (see the Meta Ads connector).