Meta Ads: changes & controls
create_meta_catalog_campaign
Launch an Advantage+ catalog (dynamic product ads) campaign, created PAUSED: create_campaign (OUTCOME_SALES, promoted_object.product_catalog_id, daily budget) -> create_ad_set (promoted_object.product
POST
Launch an Advantage+ catalog (dynamic product ads) campaign, created PAUSED: create_campaign (OUTCOME_SALES, promoted_object.product_catalog_id, daily budget) -> create_ad_set (promoted_object.product_set_id + the conversion event, OFFSITE_CONVERSIONS; with retargeting_window_days it targets people who viewed or added to cart in that window and did not buy, otherwise it is prospecting) -> create_meta_catalog_ad (a template creative on the product set). Every step is staged for dashboard approval: the tool stops at the first staged step and returns the rest; after approval use the id Meta returned in place of each {"$fromStep": n} reference.
Launch an Advantage+ catalog (dynamic product ads) campaign, created PAUSED: create_campaign (OUTCOME_SALES, promoted_object.product_catalog_id, daily budget) -> create_ad_set (promoted_object.product_set_id + the conversion event, OFFSITE_CONVERSIONS; with retargeting_window_days it targets people who viewed or added to cart in that window and did not buy, otherwise it is prospecting) -> create_meta_catalog_ad (a template creative on the product set). Every step is staged for dashboard approval: the tool stops at the first staged step and returns the rest; after approval use the id Meta returned in place of each {“$fromStep”: n} reference.
Platform: Meta Ads · Type: Change
How to call it
- MCP: on
https://mcp.adsmcp.si/mcp, run it through themeta_ads_writetool with{"action": "execute", "tool_name": "create_meta_catalog_campaign", "arguments": { ... }}, or callcreate_meta_catalog_campaignby name.search_toolsfinds it andget_tool_schemareturns its arguments;https://mcp.adsmcp.si/mcp/flatlists every tool by name. - REST:
POST https://mcp.adsmcp.si/api/v1/tools/create_meta_catalog_campaign/executewithAuthorization: Bearer sk_live_...and a JSON body{"platform": "meta", "arguments": { ... }}. The arguments are listed below; they are exactly the tool’s input schema.