Update to W. Google Merchant Center

{
  "description": "Analyze Google Merchant Center product feed and Shopping data through Windsor.ai. Use when the user asks about their Merchant Center product feed — product status, disapprovals and issues, availability, clicks, impressions, CTR, or price benchmarks by product, brand, or category. This connector is read-only — it has no write actions and cannot edit the product feed. Do not use for Google Ads Shopping campaign spend or ROAS (those live in the Google Ads connector), other platforms (e.g. Amazon), or fixing/updating feed data.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 523
    }
  ],
  "name": "google-merchant-center",
  "skill_md_contents": "---\nname: google-merchant-center\ndescription: Analyze Google Merchant Center product feed and Shopping data through Windsor.ai. Use when the user asks about their Merchant Center product feed — product status, disapprovals and issues, availability, clicks, impressions, CTR, or price benchmarks by product, brand, or category. This connector is read-only — it has no write actions and cannot edit the product feed. Do not use for Google Ads Shopping campaign spend or ROAS (those live in the Google Ads connector), other platforms (e.g. Amazon), or fixing/updating feed data.\n---\n\n# Google Merchant Center via Windsor.ai\n\nWindsor.ai pulls Google Merchant Center product feed and Shopping data. The\nconnector id is `google_merchant`. On the Google Merchant Center app the\nconnector is already scoped, so you usually do not need to pass it — but when\na tool asks for a connector, use `google_merchant`.\n\nThis connector is **read-only** product feed and Shopping analytics. It has\n**no Google Ads Shopping campaign data** (spend and ROAS live in the Google\nAds connector, so route those questions there), and it does **not** edit the\nproduct feed or fix disapproved products — there are no write actions. If\nasked to change GTINs, prices, or other feed data, say that's out of scope\nhere.\n\nGolden rules:\n\n- **Never guess field, account, or option names** — get them from\n  `get_fields`, `get_connectors`, and `get_options`. Call those first.\n- Read-only connector; there are no live write actions to run.\n- Report what the user asked for, concisely.\n\n## 1. Ground yourself first\n\nCall `get_connectors` to see which Merchant Center accounts are connected\n(each has an id and, usually, a name). If none is connected, help the user\nconnect one: call `get_connector_authorization_url` (or\n`get_connector_connect_info` for the auth type and steps) and give them the\nsetup link — do not describe manual 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 Merchant Center data\n\n1. Call `get_fields` for `google_merchant` to get valid field ids — product\n   and feed attributes (product status, disapproval reasons/issues,\n   availability, price, price benchmark, brand, category) and Shopping\n   performance metrics (clicks, impressions, CTR). Use the exact ids\n   returned, not these examples.\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-02-01\"`), or\n     `date_preset` — `last_7d`, `last_30d`, `this_month`; append `T` to\n     include today (e.g. `last_7dT`, `this_monthT`).\n   - `filters`: optional conditions, e.g. filtering to disapproved products or\n     to a price-benchmark threshold; combine with `\"and\"`/`\"or\"` as needed.\n\nMerchant Center specifics to respect:\n\n- Feed/status attributes (approval status, disapproval reasons, availability,\n  price, price benchmark) describe the **current state of the feed**, while\n  clicks, impressions, and CTR are **per-day performance metrics** over the\n  requested range. Don't present a current feed attribute as if it varied\n  over a historical date range.\n- When surfacing disapprovals, include the issue/reason field alongside the\n  product so the user knows what to fix — even though this connector can't\n  fix it for them.\n\nCommon requests → recipe:\n\n- **Disapproved products:** fields for product, status, and disapproval\n  issues; filter to the disapproved status.\n- **High impressions, low CTR:** fields for product, impressions, clicks\n  (or CTR), over a date range; rank by impressions and CTR in your answer.\n- **Price benchmarking:** fields for product price and price benchmark;\n  compare and flag products priced above or below benchmark.\n\nIf a field the user wants isn't in `get_fields`, say so rather than\nsubstituting a different metric. There is no ad spend or campaign data here.\n\n## 3. Reference real data, don't fabricate\n\nOn an error (unknown field/connector/account), call the relevant discovery\ntool and retry with correct ids, or report the specific error. Never invent\nproduct statuses, disapproval reasons, click or impression counts, or price\nfigures.\n"
}