Amazon Ads
Read and change campaigns, ad groups and targets, read ads, accounts and recommendations, and request reports.
An Amazon Ads connection comes in two forms, and both sign in with Amazon in the region of your advertiser account, North America, Europe or the Far East. Amazon Ads gives a playbook's functions the Amazon Ads API, from eleven operations of Amazon's unified document: connected with an advertiser account's ID, it acts on that account; connected without one, it lists the accounts you reach. Amazon Ads MCP gives them Amazon's Ads MCP server for the same region, which reads and manages campaigns, ad groups, ads, targets and reports.
Available on Auto Cloud and on self-hosted runtimes.
What a playbook can do with Amazon Ads
- List the advertiser accounts you reach, and read an account's campaigns, ad groups, ads and targets.
- Read Amazon's recommendations for an account.
- Create and change campaigns, ad groups and targets.
- Request a report, and read it once Amazon has made it. A report's file is a download that a call does not fetch; the operation answers where it is.
The queries of accounts, campaigns, ad groups, ads, targets and recommendations, and the retrieval of a report, are marked as tools that only read; creating a report counts as an act, since Amazon keeps it.
The tools of Amazon Ads, as the connection lists them
Tools that read: QueryAdvertiserAccount, QueryCampaign, QueryAdGroup, QueryAd, QueryTarget, AdsApiv1RetrieveReport and QueryRecommendation.
Tools that act: UpdateCampaign, UpdateAdGroup, UpdateTarget and AdsApiv1CreateReport.
Amazon Ads MCP: its MCP server lists its own tools when a function runs, and once you connect, your agent lists them with list_connection_tools.
An example workflow
Acting on Amazon's recommendations the way your account manager would. A schedule trigger runs the workflow every Tuesday. A lookup function reads the account's recommendations with QueryRecommendation, and another reads the campaigns and targets they refer to. A reasoning function reads each recommendation with the account's rules in its prompt, the margin floor, the brands it never bids on, the campaigns under test, and sorts them into accept, decline and ask. An interaction function sends the ones to ask to the account manager through a Slack connection and waits for the answers. Accepted bid changes go through the target operation, one interaction function run each, and the run's history in Studio keeps the recommendation, the decision and the change. Nothing Amazon suggested is applied without the rules or a person saying so.
How to connect Amazon Ads
Amazon Ads
- Sign in with Amazon and allow Amazon Ads campaign management. The consent screen shows the permissions listed below.
Amazon Ads MCP
- Sign in with Amazon and allow Amazon Ads campaign management. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect Amazon Ads to Auto, or open Settings, Agents, Connections in Auto Studio and choose Amazon Ads or Amazon Ads MCP.
- On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
- Have your agent check one small read through the connection before a function depends on it.
Amazon Ads asks for these values when you connect:
| Value | What it is |
|---|---|
region | The region of your advertiser account, which sets the host of the Amazon Ads API and the Login with Amazon hosts a person signs in at and the tokens come from. One of North America (na), Europe (eu) or Far East (fe). |
account_id, optional | The ID of the Amazon Ads advertiser account the connection acts on, which QueryAdvertiserAccount lists; leave it empty to connect without one and list the accounts. |
Amazon Ads MCP asks for one value when you connect:
| Value | What it is |
|---|---|
region | The region of your advertiser account, which sets the host of the Amazon Ads MCP server. One of North America (na), Europe (eu) or Far East (fe). |
What it needs
- An Amazon account with access to the advertiser accounts, in the Amazon Ads console of their region.
- Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection.
- On a self-hosted runtime, a Login with Amazon security profile of your own with access to the Amazon Ads API, registered as the runtime's client, as Let people add connections sets out; Amazon answers the client of a security profile it gave access alone.
Permissions Auto asks for
Amazon Ads and Amazon Ads MCP:
- Read and manage the campaigns, ad groups, ads, targets and reports of Amazon Ads advertiser accounts.
Good to know
Connect once without an account ID to see which accounts you reach, then connect the account a playbook works on by its ID, so the connection acts on one account and no other. A report takes Amazon a while to make; a workflow requests it in one step and reads it in a later one. What a function reads is kept in the run's history, where people with access to the playbook can read it.