Update to Facebook Ads by Windsor.ai
Snapshot Nov 19, 2026 · 00:10 UTC · version 2.0.7
Collection source: downloaded plugin package.
Instructions updated for facebook-ads
Full description — Now says: campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Oct 29, 2026 · 12:05 UTC
live campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, chan...
Nov 19, 2026 · 00:10 UTC
campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a ...
Skill instructions
Oct 29, 2026 · 12:05 UTC
live campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, chan...
Nov 19, 2026 · 00:10 UTC
campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a ...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,11 +1,11 @@ --- name: facebook-ads -description: Analyze and manage Meta Ads (Facebook & Instagram ad placements) through Windsor.ai. Use when the user asks about their Facebook Ads / Meta Ads performance — pulling live campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a budget, boost an existing post, or edit ad creative. Do not use for other ad platforms (Google Ads, TikTok, LinkedIn, Microsoft Ads), organic Facebook Page posts or Instagram organic content, or designing/generating ad creative images. +description: Analyze and manage Meta Ads (Facebook & Instagram ad placements) through Windsor.ai. Use when the user asks about their Facebook Ads / Meta Ads performance — pulling campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a budget, boost an existing post, edit ad creative or targeting, duplicate an ad set, look up targeting interests or locations, or create a lead form (Instant Form). Do not use for other ad platforms (Google Ads, TikTok, LinkedIn, Microsoft Ads), organic Facebook Page posts or Instagram organic content, or designing/generating ad creative images. --- # Facebook Ads via Windsor.ai -Windsor.ai exposes live Meta Ads data (read) and a set of campaign management +Windsor.ai exposes Meta Ads data (read) and a set of campaign management actions (write) for Facebook and Instagram ad placements through MCP tools. The connector id is `facebook`. On the Facebook Ads app the connector is already scoped, so you usually do not need to pass it — but when a tool asks @@ -101,6 +101,37 @@ the post as the creative; created paused). - **Messaging:** `set_page_welcome_message` (set the automated greeting shown when someone opens a conversation from a Click-to-Message ad). +- **Duplicate:** `duplicate_adset` copies an ad set with its targeting, budget + and schedule, into the same campaign or another one (`campaign_id`), and + with its ads when `deep_copy` is true. The copy is paused unless + `status_option` says otherwise. There is no delete action, so a copy can be + paused but not removed: confirm before copying, and do not repeat a copy + that reported a partial result. +- **Images and video:** `create_ad_image` uploads image files from the chat + (it has `requires_files`, so it runs through `upload_files`) and returns one + `image_hash` per image for `create_ad`. `create_ad_video` takes a public + `video_url`, waits for Meta to process it and returns a `video_id` for + `create_ad`, which then also needs a thumbnail. If Meta cannot fetch the + video, report the error and ask for another URL; do not retry the same one. + Uploads cannot be undone by an action. +- **Lead forms:** `create_lead_form` creates an Instant Form on a Facebook + Page (questions, privacy policy URL, optional intro screen and end-screen + link). Attach it in `create_ad` through + `object_story_spec.link_data.call_to_action.value.lead_gen_form_id`, in an ad + set with `destination_type` ON_AD of an OUTCOME_LEADS campaign. Meta does + not allow editing or deleting a form: create a new one and archive the old + one with `set_lead_form_status`. The connected Facebook user needs the + Advertise task on the page. +- **Targeting lookups:** `search_targeting` (interests, behaviors, job titles + and other demographics, by keyword) and `search_locations` (countries, + regions, cities, postal codes) are read-only and return the ids and keys + that `create_adset` and `update_adset` take in `targeting`. They change + nothing, so they need no confirmation. Never invent a targeting id: look it + up, and check that each returned name fits what the user meant, because + Meta returns broad suggestions when nothing matches. + +An action named above that `list_actions` does not return is not available on +this connection yet: say so, and do not try to run it. Budget and creation mechanics: @@ -109,8 +140,8 @@ - Budget actions (`set_campaign_budget`, `set_adset_budget`, `spend_cap`) set an **absolute** value, not a delta. To "raise by 20%", read the current value first, compute the new absolute amount, and set that. -- `create_campaign`, `create_adset`, `create_ad`, and `boost_post` all - produce **paused** objects by default, so nothing spends until the user +- `create_campaign`, `create_adset`, `create_ad`, `boost_post` and + `duplicate_adset` all produce **paused** objects by default, so nothing spends until the user enables it. Write workflow — every time:
Full technical diff · 2 changed fields
changed /description
"Analyze and manage Meta Ads (Facebook & Instagram ad placements) through Windsor.ai. Use when the user asks about their Facebook Ads / Meta Ads performance — pulling live campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a budget, boost an existing post, or edit ad creative. Do not use for other ad platforms (Google Ads, TikTok, LinkedIn, Microsoft Ads), organic Facebook Page posts or Instagram organic content, or designing/generating ad creative images."
"Analyze and manage Meta Ads (Facebook & Instagram ad placements) through Windsor.ai. Use when the user asks about their Facebook Ads / Meta Ads performance — pulling campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a budget, boost an existing post, edit ad creative or targeting, duplicate an ad set, look up targeting interests or locations, or create a lead form (Instant Form). Do not use for other ad platforms (Google Ads, TikTok, LinkedIn, Microsoft Ads), organic Facebook Page posts or Instagram organic content, or designing/generating ad creative images."
changed /skill_md_contents
"---\nname: facebook-ads\ndescription: Analyze and manage Meta Ads (Facebook & Instagram ad placements) through Windsor.ai. Use when the user asks about their Facebook Ads / Meta Ads performance — pulling live campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a budget, boost an existing post, or edit ad creative. Do not use for other ad platforms (Google Ads, TikTok, LinkedIn, Microsoft Ads), organic Facebook Page posts or Instagram organic content, or designing/generating ad creative images.\n---\n\n# Facebook Ads via Windsor.ai\n\nWindsor.ai exposes live Meta Ads data (read) and a set of campaign management\nactions (write) for Facebook and Instagram ad placements through MCP tools.\nThe connector id is `facebook`. On the Facebook Ads app the connector is\nalready scoped, so you usually do not need to pass it — but when a tool asks\nfor a connector, use `facebook`.\n\nThis connector covers **Meta Ads** (paid Facebook & Instagram ad placements)\nonly. It is distinct from Facebook Organic (Page posts) and Instagram\norganic, which live in their own connectors — route organic questions there.\n\nGolden rules:\n\n- **Never guess field, account, action, or option names.** They come from\n `get_fields`, `get_connectors`, `list_actions`, and `get_options`. Call those\n first; do not invent identifiers.\n- **Reads are safe; writes change live ad spend.** Only call `execute_action`\n after the user has confirmed the specific change.\n- Report numbers the user asked for, concisely. Don't dump raw rows unless asked.\n\n## 1. Ground yourself first\n\nCall `get_connectors` to see which Meta Ads accounts are connected (each has\nan id and, usually, a name). If none are connected, help the user connect one:\ncall `get_connector_authorization_url` (or `get_connector_connect_info` for the\nauth type and steps) and give them the setup link — do not describe manual\ndashboard navigation.\n\nIf the user names an account, match it to a connected account id. If several are\nconnected and the request is ambiguous, ask which account.\n\n## 2. Reading performance data\n\n1. Call `get_fields` for `facebook` to get valid field ids (e.g. campaign,\n ad set, ad, date, spend, impressions, clicks, conversions, purchases — use\n the exact ids returned, not these examples).\n2. If the analysis needs attribution windows or other segmentation controls,\n call `get_options` to see the connector's options and valid values (e.g.\n click/view attribution windows).\n3. Call `get_data` with:\n - `fields`: the ids you actually need (keep the set small).\n - `accounts`: the target account id(s); omit for all connected accounts.\n - A date range: either `date_from`/`date_to` (`\"2026-02-01\"`), or\n `date_preset` — `last_7d`, `last_30d`, `last_Xd`/`last_Xw`/`last_Xm`,\n `this_month`, `this_year`, `last_year`. Append `T` to include today\n (e.g. `last_7dT`, `this_monthT`).\n - `options`: only if get_options showed relevant ones.\n - `filters`: optional conditions, e.g. `[[\"spend\", \"gt\", 100]]`; combine\n with `\"and\"`/`\"or\"` and nest as needed.\n\nCommon requests → recipe:\n\n- **Overview / trend:** fields `date` + the metrics, over a preset range.\n- **By campaign / ad set / ad:** fields campaign/ad set/ad + metrics; sort or\n aggregate in your answer.\n- **Best / worst campaign:** pull campaign + the metric, then rank; return only\n what was asked (e.g. just the campaign name) if the user constrained the\n output format.\n- **Efficiency:** cost per result = spend ÷ conversions (or purchases); ROAS =\n purchase value ÷ spend. Compute from returned fields; note if the\n denominator is zero.\n\nWatch out: Meta spend fields are in the account currency (state it if known).\nIf a field the user wants isn't in `get_fields`, say so rather than\nsubstituting a different metric.\n\n## 3. Managing campaigns (write actions)\n\nMeta Ads exposes a set of write actions via `list_actions` / `execute_action`.\nAlways call `list_actions` first for the exact ids and JSON schemas — treat\nthe summary below as guidance, not gospel. They cover:\n\n- **Create / structure:** `create_campaign` (Facebook or Instagram, with an\n objective such as OUTCOME_TRAFFIC/OUTCOME_LEADS/OUTCOME_SALES and any\n required `special_ad_categories`; created paused), `create_adset` (in an\n existing campaign, with targeting, optimization goal, and billing event;\n created paused), `create_ad` (in an existing ad set — either a simple\n link-ad builder from page_id/link/message/image_url/call_to_action_type, a\n Click-to-Message ad via `messaging_destination`, or a raw creative spec;\n created paused).\n- **Status:** `pause_campaign` / `enable_campaign`, `pause_adset` /\n `enable_adset`, `pause_ad` / `enable_ad`.\n- **Budget:** `set_campaign_budget` and `set_adset_budget` (`daily` or\n `lifetime`; setting one budget type replaces the other).\n- **Update existing objects:** `update_campaign` (name, bid_strategy,\n special_ad_categories, spend_cap), `update_adset` (name, targeting,\n optimization_goal, bid_amount/bid_strategy, destination_type, end_time),\n `update_ad` (name, creative reference, conversion_domain,\n display_sequence), `update_ad_creative` (edits an ad's copy, headline,\n description, link, image, call-to-action, URL tags, or one carousel card —\n Meta treats creatives as immutable, so this creates a new creative and\n re-points the ad at it).\n- **Organic post promotion:** `boost_post` (turn an existing organic Facebook\n or Instagram post into a paid ad in an existing engagement ad set, reusing\n the post as the creative; created paused).\n- **Messaging:** `set_page_welcome_message` (set the automated greeting shown\n when someone opens a conversation from a Click-to-Message ad).\n\nBudget and creation mechanics:\n\n- Money amounts are in the account currency's **minor unit** (e.g. cents):\n `5000` means 50.00 — not micros. Convert the user's amount before calling.\n- Budget actions (`set_campaign_budget`, `set_adset_budget`, `spend_cap`) set\n an **absolute** value, not a delta. To \"raise by 20%\", read the current\n value first, compute the new absolute amount, and set that.\n- `create_campaign`, `create_adset`, `create_ad`, and `boost_post` all\n produce **paused** objects by default, so nothing spends until the user\n enables it.\n\nWrite workflow — every time:\n\n1. Resolve the campaign/ad set/ad to its id (via a `get_data` read on the\n relevant name and id fields if the user gave a name).\n2. Build the exact params from the `list_actions` schema.\n3. **Show the user the concrete change and ask them to confirm** — e.g.\n \"Pause campaign 'Summer Sale' (id 123…) on account 456…?\" or \"Set daily\n budget for ad set X to €50.00 (5000 in minor units)?\".\n4. Only after an explicit yes, call `execute_action` and report the result.\n\nIf the user says \"pause the worst campaign\", first do the read + ranking, then\nname the specific campaign and confirm before pausing — don't pause on the\nstrength of the aggregate alone.\n\n## 4. Reference the user's data, don't fabricate\n\nIf a tool returns an error (unknown field/connector/account), call the relevant\ndiscovery tool (`get_fields`, `get_connectors`, `list_actions`) and retry with\ncorrect ids. Never fill gaps with made-up numbers or campaign names.\n"
"---\nname: facebook-ads\ndescription: Analyze and manage Meta Ads (Facebook & Instagram ad placements) through Windsor.ai. Use when the user asks about their Facebook Ads / Meta Ads performance — pulling campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a budget, boost an existing post, edit ad creative or targeting, duplicate an ad set, look up targeting interests or locations, or create a lead form (Instant Form). Do not use for other ad platforms (Google Ads, TikTok, LinkedIn, Microsoft Ads), organic Facebook Page posts or Instagram organic content, or designing/generating ad creative images.\n---\n\n# Facebook Ads via Windsor.ai\n\nWindsor.ai exposes Meta Ads data (read) and a set of campaign management\nactions (write) for Facebook and Instagram ad placements through MCP tools.\nThe connector id is `facebook`. On the Facebook Ads app the connector is\nalready scoped, so you usually do not need to pass it — but when a tool asks\nfor a connector, use `facebook`.\n\nThis connector covers **Meta Ads** (paid Facebook & Instagram ad placements)\nonly. It is distinct from Facebook Organic (Page posts) and Instagram\norganic, which live in their own connectors — route organic questions there.\n\nGolden rules:\n\n- **Never guess field, account, action, or option names.** They come from\n `get_fields`, `get_connectors`, `list_actions`, and `get_options`. Call those\n first; do not invent identifiers.\n- **Reads are safe; writes change live ad spend.** Only call `execute_action`\n after the user has confirmed the specific change.\n- Report numbers the user asked for, concisely. Don't dump raw rows unless asked.\n\n## 1. Ground yourself first\n\nCall `get_connectors` to see which Meta Ads accounts are connected (each has\nan id and, usually, a name). If none are connected, help the user connect one:\ncall `get_connector_authorization_url` (or `get_connector_connect_info` for the\nauth type and steps) and give them the setup link — do not describe manual\ndashboard navigation.\n\nIf the user names an account, match it to a connected account id. If several are\nconnected and the request is ambiguous, ask which account.\n\n## 2. Reading performance data\n\n1. Call `get_fields` for `facebook` to get valid field ids (e.g. campaign,\n ad set, ad, date, spend, impressions, clicks, conversions, purchases — use\n the exact ids returned, not these examples).\n2. If the analysis needs attribution windows or other segmentation controls,\n call `get_options` to see the connector's options and valid values (e.g.\n click/view attribution windows).\n3. Call `get_data` with:\n - `fields`: the ids you actually need (keep the set small).\n - `accounts`: the target account id(s); omit for all connected accounts.\n - A date range: either `date_from`/`date_to` (`\"2026-02-01\"`), or\n `date_preset` — `last_7d`, `last_30d`, `last_Xd`/`last_Xw`/`last_Xm`,\n `this_month`, `this_year`, `last_year`. Append `T` to include today\n (e.g. `last_7dT`, `this_monthT`).\n - `options`: only if get_options showed relevant ones.\n - `filters`: optional conditions, e.g. `[[\"spend\", \"gt\", 100]]`; combine\n with `\"and\"`/`\"or\"` and nest as needed.\n\nCommon requests → recipe:\n\n- **Overview / trend:** fields `date` + the metrics, over a preset range.\n- **By campaign / ad set / ad:** fields campaign/ad set/ad + metrics; sort or\n aggregate in your answer.\n- **Best / worst campaign:** pull campaign + the metric, then rank; return only\n what was asked (e.g. just the campaign name) if the user constrained the\n output format.\n- **Efficiency:** cost per result = spend ÷ conversions (or purchases); ROAS =\n purchase value ÷ spend. Compute from returned fields; note if the\n denominator is zero.\n\nWatch out: Meta spend fields are in the account currency (state it if known).\nIf a field the user wants isn't in `get_fields`, say so rather than\nsubstituting a different metric.\n\n## 3. Managing campaigns (write actions)\n\nMeta Ads exposes a set of write actions via `list_actions` / `execute_action`.\nAlways call `list_actions` first for the exact ids and JSON schemas — treat\nthe summary below as guidance, not gospel. They cover:\n\n- **Create / structure:** `create_campaign` (Facebook or Instagram, with an\n objective such as OUTCOME_TRAFFIC/OUTCOME_LEADS/OUTCOME_SALES and any\n required `special_ad_categories`; created paused), `create_adset` (in an\n existing campaign, with targeting, optimization goal, and billing event;\n created paused), `create_ad` (in an existing ad set — either a simple\n link-ad builder from page_id/link/message/image_url/call_to_action_type, a\n Click-to-Message ad via `messaging_destination`, or a raw creative spec;\n created paused).\n- **Status:** `pause_campaign` / `enable_campaign`, `pause_adset` /\n `enable_adset`, `pause_ad` / `enable_ad`.\n- **Budget:** `set_campaign_budget` and `set_adset_budget` (`daily` or\n `lifetime`; setting one budget type replaces the other).\n- **Update existing objects:** `update_campaign` (name, bid_strategy,\n special_ad_categories, spend_cap), `update_adset` (name, targeting,\n optimization_goal, bid_amount/bid_strategy, destination_type, end_time),\n `update_ad` (name, creative reference, conversion_domain,\n display_sequence), `update_ad_creative` (edits an ad's copy, headline,\n description, link, image, call-to-action, URL tags, or one carousel card —\n Meta treats creatives as immutable, so this creates a new creative and\n re-points the ad at it).\n- **Organic post promotion:** `boost_post` (turn an existing organic Facebook\n or Instagram post into a paid ad in an existing engagement ad set, reusing\n the post as the creative; created paused).\n- **Messaging:** `set_page_welcome_message` (set the automated greeting shown\n when someone opens a conversation from a Click-to-Message ad).\n- **Duplicate:** `duplicate_adset` copies an ad set with its targeting, budget\n and schedule, into the same campaign or another one (`campaign_id`), and\n with its ads when `deep_copy` is true. The copy is paused unless\n `status_option` says otherwise. There is no delete action, so a copy can be\n paused but not removed: confirm before copying, and do not repeat a copy\n that reported a partial result.\n- **Images and video:** `create_ad_image` uploads image files from the chat\n (it has `requires_files`, so it runs through `upload_files`) and returns one\n `image_hash` per image for `create_ad`. `create_ad_video` takes a public\n `video_url`, waits for Meta to process it and returns a `video_id` for\n `create_ad`, which then also needs a thumbnail. If Meta cannot fetch the\n video, report the error and ask for another URL; do not retry the same one.\n Uploads cannot be undone by an action.\n- **Lead forms:** `create_lead_form` creates an Instant Form on a Facebook\n Page (questions, privacy policy URL, optional intro screen and end-screen\n link). Attach it in `create_ad` through\n `object_story_spec.link_data.call_to_action.value.lead_gen_form_id`, in an ad\n set with `destination_type` ON_AD of an OUTCOME_LEADS campaign. Meta does\n not allow editing or deleting a form: create a new one and archive the old\n one with `set_lead_form_status`. The connected Facebook user needs the\n Advertise task on the page.\n- **Targeting lookups:** `search_targeting` (interests, behaviors, job titles\n and other demographics, by keyword) and `search_locations` (countries,\n regions, cities, postal codes) are read-only and return the ids and keys\n that `create_adset` and `update_adset` take in `targeting`. They change\n nothing, so they need no confirmation. Never invent a targeting id: look it\n up, and check that each returned name fits what the user meant, because\n Meta returns broad suggestions when nothing matches.\n\nAn action named above that `list_actions` does not return is not available on\nthis connection yet: say so, and do not try to run it.\n\nBudget and creation mechanics:\n\n- Money amounts are in the account currency's **minor unit** (e.g. cents):\n `5000` means 50.00 — not micros. Convert the user's amount before calling.\n- Budget actions (`set_campaign_budget`, `set_adset_budget`, `spend_cap`) set\n an **absolute** value, not a delta. To \"raise by 20%\", read the current\n value first, compute the new absolute amount, and set that.\n- `create_campaign`, `create_adset`, `create_ad`, `boost_post` and\n `duplicate_adset` all produce **paused** objects by default, so nothing spends until the user\n enables it.\n\nWrite workflow — every time:\n\n1. Resolve the campaign/ad set/ad to its id (via a `get_data` read on the\n relevant name and id fields if the user gave a name).\n2. Build the exact params from the `list_actions` schema.\n3. **Show the user the concrete change and ask them to confirm** — e.g.\n \"Pause campaign 'Summer Sale' (id 123…) on account 456…?\" or \"Set daily\n budget for ad set X to €50.00 (5000 in minor units)?\".\n4. Only after an explicit yes, call `execute_action` and report the result.\n\nIf the user says \"pause the worst campaign\", first do the read + ranking, then\nname the specific campaign and confirm before pausing — don't pause on the\nstrength of the aggregate alone.\n\n## 4. Reference the user's data, don't fabricate\n\nIf a tool returns an error (unknown field/connector/account), call the relevant\ndiscovery tool (`get_fields`, `get_connectors`, `list_actions`) and retry with\ncorrect ids. Never fill gaps with made-up numbers or campaign names.\n"
Full snapshot data
{
"description": "Analyze and manage Meta Ads (Facebook & Instagram ad placements) through Windsor.ai. Use when the user asks about their Facebook Ads / Meta Ads performance — pulling campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a budget, boost an existing post, edit ad creative or targeting, duplicate an ad set, look up targeting interests or locations, or create a lead form (Instant Form). Do not use for other ad platforms (Google Ads, TikTok, LinkedIn, Microsoft Ads), organic Facebook Page posts or Instagram organic content, or designing/generating ad creative images.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 517
}
],
"name": "facebook-ads",
"skill_md_contents": "---\nname: facebook-ads\ndescription: Analyze and manage Meta Ads (Facebook & Instagram ad placements) through Windsor.ai. Use when the user asks about their Facebook Ads / Meta Ads performance — pulling campaign, ad set, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to create, pause, or enable a campaign, ad set, or ad, change a budget, boost an existing post, edit ad creative or targeting, duplicate an ad set, look up targeting interests or locations, or create a lead form (Instant Form). Do not use for other ad platforms (Google Ads, TikTok, LinkedIn, Microsoft Ads), organic Facebook Page posts or Instagram organic content, or designing/generating ad creative images.\n---\n\n# Facebook Ads via Windsor.ai\n\nWindsor.ai exposes Meta Ads data (read) and a set of campaign management\nactions (write) for Facebook and Instagram ad placements through MCP tools.\nThe connector id is `facebook`. On the Facebook Ads app the connector is\nalready scoped, so you usually do not need to pass it — but when a tool asks\nfor a connector, use `facebook`.\n\nThis connector covers **Meta Ads** (paid Facebook & Instagram ad placements)\nonly. It is distinct from Facebook Organic (Page posts) and Instagram\norganic, which live in their own connectors — route organic questions there.\n\nGolden rules:\n\n- **Never guess field, account, action, or option names.** They come from\n `get_fields`, `get_connectors`, `list_actions`, and `get_options`. Call those\n first; do not invent identifiers.\n- **Reads are safe; writes change live ad spend.** Only call `execute_action`\n after the user has confirmed the specific change.\n- Report numbers the user asked for, concisely. Don't dump raw rows unless asked.\n\n## 1. Ground yourself first\n\nCall `get_connectors` to see which Meta Ads accounts are connected (each has\nan id and, usually, a name). If none are connected, help the user connect one:\ncall `get_connector_authorization_url` (or `get_connector_connect_info` for the\nauth type and steps) and give them the setup link — do not describe manual\ndashboard navigation.\n\nIf the user names an account, match it to a connected account id. If several are\nconnected and the request is ambiguous, ask which account.\n\n## 2. Reading performance data\n\n1. Call `get_fields` for `facebook` to get valid field ids (e.g. campaign,\n ad set, ad, date, spend, impressions, clicks, conversions, purchases — use\n the exact ids returned, not these examples).\n2. If the analysis needs attribution windows or other segmentation controls,\n call `get_options` to see the connector's options and valid values (e.g.\n click/view attribution windows).\n3. Call `get_data` with:\n - `fields`: the ids you actually need (keep the set small).\n - `accounts`: the target account id(s); omit for all connected accounts.\n - A date range: either `date_from`/`date_to` (`\"2026-02-01\"`), or\n `date_preset` — `last_7d`, `last_30d`, `last_Xd`/`last_Xw`/`last_Xm`,\n `this_month`, `this_year`, `last_year`. Append `T` to include today\n (e.g. `last_7dT`, `this_monthT`).\n - `options`: only if get_options showed relevant ones.\n - `filters`: optional conditions, e.g. `[[\"spend\", \"gt\", 100]]`; combine\n with `\"and\"`/`\"or\"` and nest as needed.\n\nCommon requests → recipe:\n\n- **Overview / trend:** fields `date` + the metrics, over a preset range.\n- **By campaign / ad set / ad:** fields campaign/ad set/ad + metrics; sort or\n aggregate in your answer.\n- **Best / worst campaign:** pull campaign + the metric, then rank; return only\n what was asked (e.g. just the campaign name) if the user constrained the\n output format.\n- **Efficiency:** cost per result = spend ÷ conversions (or purchases); ROAS =\n purchase value ÷ spend. Compute from returned fields; note if the\n denominator is zero.\n\nWatch out: Meta spend fields are in the account currency (state it if known).\nIf a field the user wants isn't in `get_fields`, say so rather than\nsubstituting a different metric.\n\n## 3. Managing campaigns (write actions)\n\nMeta Ads exposes a set of write actions via `list_actions` / `execute_action`.\nAlways call `list_actions` first for the exact ids and JSON schemas — treat\nthe summary below as guidance, not gospel. They cover:\n\n- **Create / structure:** `create_campaign` (Facebook or Instagram, with an\n objective such as OUTCOME_TRAFFIC/OUTCOME_LEADS/OUTCOME_SALES and any\n required `special_ad_categories`; created paused), `create_adset` (in an\n existing campaign, with targeting, optimization goal, and billing event;\n created paused), `create_ad` (in an existing ad set — either a simple\n link-ad builder from page_id/link/message/image_url/call_to_action_type, a\n Click-to-Message ad via `messaging_destination`, or a raw creative spec;\n created paused).\n- **Status:** `pause_campaign` / `enable_campaign`, `pause_adset` /\n `enable_adset`, `pause_ad` / `enable_ad`.\n- **Budget:** `set_campaign_budget` and `set_adset_budget` (`daily` or\n `lifetime`; setting one budget type replaces the other).\n- **Update existing objects:** `update_campaign` (name, bid_strategy,\n special_ad_categories, spend_cap), `update_adset` (name, targeting,\n optimization_goal, bid_amount/bid_strategy, destination_type, end_time),\n `update_ad` (name, creative reference, conversion_domain,\n display_sequence), `update_ad_creative` (edits an ad's copy, headline,\n description, link, image, call-to-action, URL tags, or one carousel card —\n Meta treats creatives as immutable, so this creates a new creative and\n re-points the ad at it).\n- **Organic post promotion:** `boost_post` (turn an existing organic Facebook\n or Instagram post into a paid ad in an existing engagement ad set, reusing\n the post as the creative; created paused).\n- **Messaging:** `set_page_welcome_message` (set the automated greeting shown\n when someone opens a conversation from a Click-to-Message ad).\n- **Duplicate:** `duplicate_adset` copies an ad set with its targeting, budget\n and schedule, into the same campaign or another one (`campaign_id`), and\n with its ads when `deep_copy` is true. The copy is paused unless\n `status_option` says otherwise. There is no delete action, so a copy can be\n paused but not removed: confirm before copying, and do not repeat a copy\n that reported a partial result.\n- **Images and video:** `create_ad_image` uploads image files from the chat\n (it has `requires_files`, so it runs through `upload_files`) and returns one\n `image_hash` per image for `create_ad`. `create_ad_video` takes a public\n `video_url`, waits for Meta to process it and returns a `video_id` for\n `create_ad`, which then also needs a thumbnail. If Meta cannot fetch the\n video, report the error and ask for another URL; do not retry the same one.\n Uploads cannot be undone by an action.\n- **Lead forms:** `create_lead_form` creates an Instant Form on a Facebook\n Page (questions, privacy policy URL, optional intro screen and end-screen\n link). Attach it in `create_ad` through\n `object_story_spec.link_data.call_to_action.value.lead_gen_form_id`, in an ad\n set with `destination_type` ON_AD of an OUTCOME_LEADS campaign. Meta does\n not allow editing or deleting a form: create a new one and archive the old\n one with `set_lead_form_status`. The connected Facebook user needs the\n Advertise task on the page.\n- **Targeting lookups:** `search_targeting` (interests, behaviors, job titles\n and other demographics, by keyword) and `search_locations` (countries,\n regions, cities, postal codes) are read-only and return the ids and keys\n that `create_adset` and `update_adset` take in `targeting`. They change\n nothing, so they need no confirmation. Never invent a targeting id: look it\n up, and check that each returned name fits what the user meant, because\n Meta returns broad suggestions when nothing matches.\n\nAn action named above that `list_actions` does not return is not available on\nthis connection yet: say so, and do not try to run it.\n\nBudget and creation mechanics:\n\n- Money amounts are in the account currency's **minor unit** (e.g. cents):\n `5000` means 50.00 — not micros. Convert the user's amount before calling.\n- Budget actions (`set_campaign_budget`, `set_adset_budget`, `spend_cap`) set\n an **absolute** value, not a delta. To \"raise by 20%\", read the current\n value first, compute the new absolute amount, and set that.\n- `create_campaign`, `create_adset`, `create_ad`, `boost_post` and\n `duplicate_adset` all produce **paused** objects by default, so nothing spends until the user\n enables it.\n\nWrite workflow — every time:\n\n1. Resolve the campaign/ad set/ad to its id (via a `get_data` read on the\n relevant name and id fields if the user gave a name).\n2. Build the exact params from the `list_actions` schema.\n3. **Show the user the concrete change and ask them to confirm** — e.g.\n \"Pause campaign 'Summer Sale' (id 123…) on account 456…?\" or \"Set daily\n budget for ad set X to €50.00 (5000 in minor units)?\".\n4. Only after an explicit yes, call `execute_action` and report the result.\n\nIf the user says \"pause the worst campaign\", first do the read + ranking, then\nname the specific campaign and confirm before pausing — don't pause on the\nstrength of the aggregate alone.\n\n## 4. Reference the user's data, don't fabricate\n\nIf a tool returns an error (unknown field/connector/account), call the relevant\ndiscovery tool (`get_fields`, `get_connectors`, `list_actions`) and retry with\ncorrect ids. Never fill gaps with made-up numbers or campaign names.\n"
}SHA-256 of public snapshot: 06e09c522ab2de6fc4d8b48f7d26ccc131426131653dc3400751c876d5e77944