Amazon Ads MCP Server

Overview Schema Source Related Servers Discussions Admin

amazon ads get targets

amazon_ads_get_targets

Read-onlyIdempotent

Read one page of Amazon Sponsored Products targets, including paused and archived records by default, and continue with nextToken for the remaining results.

Instructions

Read one page of Amazon Sponsored Products targets, including paused and archived entities by default. Continue with nextToken until absent; one page is not an account total. These are configuration records, not performance metrics.

Input Schema

Name	Required	Description
`states`	No	Delivery states to include. Defaults to every state, archived included.
`accountId`	Yes	Advertising profile ID listed in AMAZON_ADS_PROFILE_IDS, such as 1234567890. The region-qualified form used by hosted getmcpads, such as EU:1234567890, is accepted when its region matches AMAZON_ADS_REGION.
`nextToken`	No	Opaque continuation token from the previous page for this same profile and filters. Omit on the first request.
`maxResults`	No	Maximum entities in this page, up to 100. Follow the returned continuation value for the rest.
`campaignIds`	No	Restrict results to these campaign IDs, as decimal strings.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations by noting default inclusion of paused and archived entities and warning that a single page is not the full account total.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences are front-loaded with the core operation and the most important caveat about pagination. Every sentence carries useful information with no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich schema, output schema, and annotations, the description supplies the remaining context an agent needs: the result type, default state inclusion, and pagination limitation. Nothing critical is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameters are already well documented. The description reinforces the default state behavior and nextToken continuation pattern, but it does not add substantial parameter-level meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: reading Amazon Sponsored Products targets. It scopes the result as configuration records rather than performance metrics and notes that paused and archived entities are included by default, which distinguishes it from report-oriented and other ad-type tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly explains pagination behavior: continue with nextToken until absent, and one page is not an account total. It also implies the right context by clarifying these are configuration records, though it does not explicitly name alternative sibling tools such as negative-target or SB/SD target tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server