_mureo-amazon-ads

Amazon Ads (official MCP, bridged by mureo)

PREREQUISITE: Read ../_mureo-shared/SKILL.md for auth, security rules, and output format — and specifically its Plugin platforms (third-party providers) section, which is the contract Amazon rides: honest scope, declaration-first guardrails, action_log promotion, structural strategy parity for mutations. This file does not repeat any of it.

Canonical platform key: plugin:mureo-amazon-ads-bridge:amazon_ads. Use it verbatim wherever a mureo surface names a platform — STATE.json platforms, mureo_state_upsert_campaign(platform="plugin:mureo-amazon-ads-bridge:amazon_ads"), mureo_state_platform_metrics_set, action_log, mureo_analytics_*. Amazon's own tools carry no mureo platform key; joining on anything else (amazon, amazon_ads, a tool namespace) silently fails to join.

The older plugin:mureo-amazon-ads-bridge form (before the key carried the provider, logly/mureo#537) stays valid on read — it resolves to the same platform, and the dashboard still labels it Amazon Ads. If STATE.json already holds an entry under it, keep writing that key: a second entry for one ad account is what double-counts it on the Reports card, and mureo never merges or rewrites either entry.

There is no mureo amazon-ads … CLI command. The only Amazon CLI is mureo amazon refresh-manifest (rebuilds the tool list). Every operation below is an MCP tool — call it directly.

What this surface is — and is not

• Amazon's own tool names, forwarded verbatim. mureo renames nothing (same treatment as the other official MCPs).
• Naming convention: <namespace>-<verb>_<resource> — the namespace is separated by a HYPHEN, with underscores inside each part (campaign_management-query_ad, account_management-query_advertiser_account). Native mureo tools are all-underscore (google_ads_campaigns_list), so any name matching, prefix filter, or "which platform is this tool" heuristic must account for the hyphen.
• The tool list is the operator's own manifest, written by mureo amazon refresh-manifest next to credentials.json and read by the mureo MCP server at start. 85 tools on the reference account. The surface can drift: if a tool named here is absent from the session, say so and suggest re-running mureo amazon refresh-manifest rather than guessing a name. mureo warns once per process when the served manifest is older than its staleness threshold — read that warning as "everything below may be out of date", and re-check before reporting a capability as missing.
• No tool declares an outputSchema (0 of 85). Response shapes are learned by calling. Only two envelopes are confirmed from live responses: campaign_management-query_campaign → {"campaigns": [...]} and campaign_management-query_ad → {"ads": [...]}. For everything else, read the actual response before you describe it — never state a field name you have not seen come back.
• Analytics are advisory. No mureo analytics module ships for Amazon (issue #120): anomaly detection, result_indicator CV-mismatch, RSA-asset audit and rule-based scoring do not exist here. Report analytics_not_available_for_plugin:mureo-amazon-ads-bridge:amazon_ads instead of inventing a heuristic from the tool schemas. The platform-agnostic analysis_anomalies_check does apply — see ../_mureo-shared/SKILL.md → Generic anomaly check.
• Guardrails are EXACT on the known money tools, with the scan as a floor under everything. A bridged manifest carries no mureo declarations, so mureo holds them itself: the 13 money-carrying tools below are declared by exact argument PATH — budgets[].budgetValue.monetaryBudgetValue.monetaryBudget.value, budgetCaps.countryMonetaryBudgetSettings.<CC>.value, bid.bid, bid.{baseBid,defaultBid,maxAverageBid} and their marketplaceSettings[] overrides — and STRATEGY.md ## Guardrails budget/bid caps are enforced on those paths, not inferred. The best-effort pattern scan still runs underneath them, and the larger amount wins, so a money field that drifted shape or that Amazon added after the snapshot falls back to that best-effort cover — a declaration can only ever raise what gets checked, never lower it. That cover is a pattern, not a guarantee: it finds the field when the new name still looks like money (budget / spend / bid, or a plain value / amount under one), so a leaf renamed to something outside that vocabulary is missed exactly as it was before the paths were declared. Any OTHER Amazon tool gets that same pattern scan on its own. An oversized or deeper-than-scannable payload fails closed with a message naming the cause. So: a cap on the tools listed below is exact and quotes the declared path when a value is unreadable; on any other Amazon write call it is strong but not guaranteed, say so in the output, and verify the resulting values after the first mutation.