Update to Windsor.ai

{
  "description": "Analyze and manage Microsoft Advertising (Bing Ads) through Windsor.ai. Use when the user asks about their Microsoft Ads performance, such as pulling live campaign, ad group, keyword, or ad metrics (spend, impressions, clicks, CTR, CPC, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns or ad groups, or when they want to pause or enable a campaign or ad group, or change a campaign's daily budget. Do not use for other ad platforms (Google Ads, Meta/Facebook Ads, TikTok Ads, LinkedIn Ads), organic Bing or web search rankings, or website analytics. Also use when the user asks how to connect Microsoft Ads (Bing Ads) to ChatGPT.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 372
    }
  ],
  "name": "microsoft-ads",
  "skill_md_contents": "---\nname: microsoft-ads\ndescription: \"Analyze and manage Microsoft Advertising (Bing Ads) through Windsor.ai. Use when the user asks about their Microsoft Ads performance, such as pulling live campaign, ad group, keyword, or ad metrics (spend, impressions, clicks, CTR, CPC, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns or ad groups, or when they want to pause or enable a campaign or ad group, or change a campaign's daily budget. Do not use for other ad platforms (Google Ads, Meta/Facebook Ads, TikTok Ads, LinkedIn Ads), organic Bing or web search rankings, or website analytics. Also use when the user asks how to connect Microsoft Ads (Bing Ads) to ChatGPT.\"\n---\n\nExplicit instructions from the user take priority over this skill.\n\n# Microsoft Ads (Bing) via Windsor.ai\n\nWindsor.ai exposes live Microsoft Advertising (Bing Ads) data (read) and a\nsmall set of campaign and ad group management actions (write) through MCP\ntools. The connector id is `bing`. Pass `bing` as the connector on every tool call; the Windsor.ai server\nserves all connectors, so it is never implied.\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 campaign/ad group status or budget.**\n  Only call `execute_action` 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. Check what is connected\n\nCall `get_connectors` to see which Microsoft Ads accounts are connected (each\nhas an id and, usually, a name). If none are connected, help the user connect\none: call `get_connector_authorization_url` (or `get_connector_connect_info`\nfor the auth type and steps) and give them the setup link; do not describe\nmanual dashboard navigation.\n\nIf the user names an account, match it to a connected account id. If several\nare connected and the request is ambiguous, ask which account.\n\n## 2. Reading Microsoft Ads data\n\n1. Call `get_fields` for `bing` to get valid field ids (e.g. campaign,\n   ad_group_name, keyword, ad_title, date, spend, impressions, clicks, CTR, CPC,\n   conversions_qualified, cost_per_conversion, revenue. Use the exact ids\n   returned, not these examples). The field `cpa` is cost per assist (spend /\n   assists), not cost per acquisition; compute CPA as spend / conversions or\n   use `cost_per_conversion`. Microsoft has deprecated `conversions`; prefer\n   `conversions_qualified`.\n2. If the analysis needs segmentation or attribution controls, call\n   `get_options` to see the connector's options and valid values.\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-07-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`); `T` works on `last_Xd`, `this_month`,\n     `this_year` and `last_year`, not on `last_Xw` or `last_Xm`.\n   - `options`: only if `get_options` showed relevant ones.\n   - `filters`: optional conditions, e.g. `[[\"spend\", \"gt\", 100]]`; combine with\n     `\"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 or ad group:** fields `campaign`/`ad_group_name` + metrics;\n  sort/aggregate in your answer.\n- **Best / worst campaign or ad group:** pull the entity + the metric, then\n  rank; return only what was asked (e.g. just the name) if the user\n  constrained the output format.\n- **Efficiency:** CPA = spend ÷ conversions; ROAS = `revenue` ÷ spend, or read `all_roas`; there is no `conversion_value` field.\n  Compute from returned fields; note if conversions are zero.\n\nWatch out: Microsoft Ads money fields are in the account currency (state it if\nknown). If a field the user wants isn't in `get_fields`, say so rather than\nsubstituting a different metric.\n\n## 3. Managing campaigns and ad groups (write actions)\n\nMicrosoft Ads exposes a small set of write actions via `list_actions` /\n`execute_action`. Always call `list_actions` first for the exact ids and JSON\nschemas, and treat the summary below as a guide. They cover:\n\n- **Status:** `pause_campaign` / `enable_campaign` (identify the campaign by\n  exactly one of `campaign_id` or `campaign_name`), and `pause_ad_group` /\n  `enable_ad_group` (identify the ad group by exactly one of `ad_group_id` or\n  `ad_group_name`, plus the parent campaign by exactly one of `campaign_id` or\n  `campaign_name`; required because ad group names are unique only within a\n  campaign).\n- **Budget:** `set_campaign_budget` sets a campaign's **daily** budget in the\n  account currency **major unit** (e.g. `50.00` means 50.00 USD on a USD\n  account; not cents, not micros). Microsoft Ads only supports daily budgets\n  at the campaign level; there is no lifetime or ad-group-level budget action.\n  If the campaign uses a shared budget, the action is **rejected** unless\n  `apply_to_shared_budget` is set to `true`, because the change would also\n  apply to every other campaign sharing that budget.\n\nThere are no campaign or ad group **creation** actions, and no keyword or\nad-level write actions; keyword and ad metrics are readable via `get_data`,\nbut writes here cover only campaign/ad group status and campaign budgets.\n\nAction names accept an id or a name directly (the action resolves\n`campaign_name` / `ad_group_name` at execution time), so a separate lookup\ncall usually isn't needed; but if the target is ambiguous (e.g. \"the\nunderperforming ad group\"), read and rank first, then confirm the specific\none.\n\nBudget mechanics:\n\n- Amounts are in the account currency **major unit**, not cents or micros.\n- `set_campaign_budget` sets an **absolute** value, not a delta. To \"raise by\n  20%\", read the current daily budget first (via `get_data`), compute the new\n  absolute amount, and set that.\n- Before setting a budget, be ready to check the shared-budget response: if\n  `execute_action` reports sibling campaigns sharing the budget, tell the user\n  which other campaigns would be affected and get their explicit go-ahead\n  before retrying with `apply_to_shared_budget=true`.\n\nWrite workflow; every time:\n\n1. Identify the target campaign (and ad group, if applicable) by id or 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 ad group 'Brand Terms' in campaign 'Q3 Sale'?\" or \"Set campaign\n   'Q3 Sale' daily budget to $75.00?\".\n4. Only after an explicit yes, call `execute_action` and report the result,\n   including any shared-budget side effects it reports.\n\nIf the user says \"pause the worst-performing ad group\", first do the read +\nranking, then name the specific ad group and confirm before pausing; don't\nact based on the totals 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\nrelevant discovery tool (`get_fields`, `get_connectors`, `list_actions`) and\nretry with correct ids. Never fill gaps with made-up numbers, campaign names,\nor ad group names.\n"
}