Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

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 by ASIN or search to preview Sponsored Products creative data 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>"
    },
    "name": "amazon_ads_get_product_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinsNoExact ten-character ASINs to read. Use this or search, not both.
limitNoMaximum products in this page, up to 100.
searchNoFree-text catalog search. Use this or asins, not both.
accountIdYesAdvertising 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.
adProductNoAd product whose eligibility rules apply: SP Sponsored Products, SB Brands, SD Display.SP
pageIndexNoZero-based page number. Use nextPageIndex from the previous call.
cursorTokenNoOpaque cursor returned by Amazon. When present it replaces pageIndex.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal 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.

  1. Changed1 schema field changedv1.0.1
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description adds real behavior context beyond them: it retrieves from the catalog without scraping retail pages, and warns that returned images 'are not complete rendered ads.' This caveat usefully sets expectations about output fidelity.

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 tight sentences, purpose front-loaded, followed by the scraping caveat and pagination mechanics. Each sentence earns its place; nothing is padded, though the phrasing is slightly terse.

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 and annotations covering the safety profile, the description only needs to convey what the tool reads and how it pages. It does both plus an image-fidelity caveat, leaving it complete enough to call correctly.

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?

With 100% schema description coverage, the schema already documents every parameter including the cursorToken-replaces-pageIndex rule. The description's pagination sentence reinforces but adds little new semantics, so the baseline 3 is appropriate.

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?

Specific verb (Read) plus an enumerated resource set (titles, native image URLs, stock, price, eligibility from the catalog), which clearly scopes this to catalog metadata rather than ad entities. It does not explicitly contrast with siblings like amazon_ads_get_product_ads, but the 'from the catalog' framing implicitly separates the two.

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?

The 'Page through pageIndex or Amazon's cursorToken' line gives pagination usage but there is no explicit when-to-use/when-not or named alternative tool. The 'use this or search, not both' guidance lives in the schema, not the description, so selection guidance here is only implied.

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