Amazon Ads anchors retail-media operations because its approved API surface spans campaign management and reporting, while its globally available open-beta MCP server gives partners with active API credentials first-party agent access to reports, campaign workflows, account settings, and financial data.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
MCP capabilities include campaign creation, update and deletion; performance and reporting queries; account-level settings; billing and financial data. Documented tools also orchestrate account creation, report generation, campaign launch, locale expansion, and end-to-end Sponsored Products setup across campaigns, ad groups, and ads.
Through the MCP server, an authorized agent can run performance and reporting queries and access account-level settings plus billing and financial data exposed by the connected Amazon Ads API credentials.
The MCP server can create, update, or delete campaigns and can orchestrate multi-step workflows such as account creation, campaign launch, locale expansion, and Sponsored Products campaign setup. Amazon's example leaves the generated campaign ready to launch and requiring review and approval.
MCP beta access is limited to Amazon Ads partners with active API credentials. Amazon Ads API access requires application and approval; a third-party application's account access is bounded by the permissions of the user who authorized it.
Amazon's documented Sponsored Products tool produces a ready-to-launch campaign that still needs review and approval. Partner policy also requires express, verifiable end-user authorization before acting on a user's behalf and prohibits sharing developer credentials with unapproved third parties.
The MCP server remains open beta and is available globally only to Amazon Ads partners with active API credentials. Amazon Ads API access is separately application- and approval-based, and Amazon has not presented the launch article as an exhaustive tool catalog.
First-party access
Agent access
Support: Official MCP server
Read scope: MCP reads cover performance and reporting queries, account-level settings, and billing or financial data available through the partner's authorized Amazon Ads API connection.
Write scope: Verified MCP writes include campaign create, update and delete plus tools for account creation, campaign launch, locale expansion, and end-to-end Sponsored Products setup; exact current tool availability still requires implementation-time inspection.
Authentication: Partner access to the open-beta MCP server depends on active Amazon Ads API credentials. API access itself is granted after Amazon's application and approval process.
Approval boundary: Keep the final review and approval outside autonomous execution for ready-to-launch campaigns, and require a fresh confirmation before campaign deletion, marketplace expansion, or any action that changes spend or exposes billing data.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Amazon ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Official Amazon Ads documentation and release notes confirm an open-beta Ads MCP server; OAuth 2.1 support is documented.
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Open beta is global for Amazon Ads partners with active API credentials; campaign create/update/delete, reporting, account settings, billing and review-before-launch are documented.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
Inventory source: structurally normalized; content was not individually reopened in this pass.
API capability and access-approval boundary
Content reviewed from the live first-party page on 2026-07-22.
Delegated application permission inheritance and revocation
Content reviewed from the live first-party announcement on 2026-07-22.
Amazon Marketing Cloud supports privacy-safe SQL analysis and audience-query workflows. Registration, geography, privacy thresholds, account eligibility, and AMC-specific permissions apply.
Targeted first-party access review
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
