Amazon Ads MCP Server

Overview Schema Source Related Servers Discussions Admin

amazon ads get product metadata

amazon_ads_get_product_metadata

Read-onlyIdempotent

Retrieve advertised product titles, image URLs, stock, price, and eligibility from an Amazon Ads catalog to validate ad product details without scraping retail pages.

Instructions

Read advertised product titles, native image URLs, stock, price and eligibility from the advertiser's Amazon catalog. Retrieves Sponsored Products visuals without scraping retail pages. Page through pageIndex or Amazon's cursorToken; product images are not complete rendered ads.

Input Schema

Name	Required	Description	Default
`asins`	No	Exact ten-character ASINs to read. Use this or search, not both.
`limit`	No	Maximum products in this page, up to 100.
`search`	No	Free-text catalog search. Use this or asins, not both.
`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.
`adProduct`	No	Ad product whose eligibility rules apply: SP Sponsored Products, SB Brands, SD Display.	SP
`pageIndex`	No	Zero-based page number. Use nextPageIndex from the previous call.
`cursorToken`	No	Opaque cursor returned by Amazon. When present it replaces pageIndex.

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

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive safety, and the description adds real context the annotations lack: data comes from the advertiser's catalog rather than retail scraping, images are native URLs, and the returned visuals are not fully rendered ads. That caveat prevents a common misinterpretation.

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

Conciseness4/5

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

Three compact sentences with the purpose front-loaded and pagination plus the image caveat last. Slightly dense phrasing ('product images are not complete rendered ads') costs a bit of clarity but nothing is wasted.

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

Completeness4/5

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

With an output schema present, return values need not be explained. The description covers purpose, data origin, and pagination, which is enough for a 7-parameter read tool; only the choice among sibling data sources remains unaddressed.

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 enumerated parameters, ASIN pattern, limit bounds, and the asins-vs-search exclusion are already documented. The description only echoes the two pagination modes, adding no syntax or constraint detail beyond the schema. Baseline 3 applies.

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

Purpose4/5

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

States a specific verb (read) and resource (advertised product titles, image URLs, stock, price, eligibility) from the advertiser's Amazon catalog. It partially differentiates from siblings by positioning itself as the Sponsored Products visual source rather than a creative-asset tool, though it never names the closest alternatives.

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

Usage Guidelines3/5

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

Usage is only implied: fetch catalog data as opposed to scraping retail pages, and page via pageIndex or cursorToken. There is no explicit statement of when to choose this over get_product_ads or list_creative_assets, which are the plausible competing sources of product/creative data.

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

Deploy Server