Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get sd creatives

amazon_ads_get_sd_creatives
Read-onlyIdempotent

Access and retrieve Sponsored Display creative assets. Use specific account and ad group IDs to read the assigned creative content for your advertising campaigns.

Instructions

Read one page of Sponsored Display creatives. Requires Display eligibility. Pagination uses startIndex, not a cursor; full pages are conservatively marked partial. Creatives include native media references; these records are not performance metrics.

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>",
      "adGroupIds": "<adGroupIds>"
    },
    "name": "amazon_ads_get_sd_creatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoMaximum entities in this page, up to 100.
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.
adGroupIdsYesSponsored Display ad group IDs whose creatives to read. Required by Amazon.
startIndexNoZero-based offset of the first entity. Use nextStartIndex from the previous page.

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

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: pagination is offset-based rather than cursor-based, full pages are conservatively flagged partial (so the agent must not treat 'partial' as truncation), and the returned records carry native media references rather than metrics.

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?

Four short sentences, front-loaded with purpose, then prerequisites, then paging behavior, then a scope caveat about the payload. Nothing is redundant with the schema.

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?

With an output schema present and rich annotations, the description only needs to cover eligibility, paging, and payload scope — and it does all three, including the misleading-'partial'-flag quirk an agent would otherwise misread.

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

Parameters4/5

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

Schema description coverage is 100%, so the parameter baseline is 3, but the description still adds value by stating that paging is via startIndex rather than a cursor, disambiguating how count/startIndex combine. It does not add anything beyond the schema for accountId or adGroupIds.

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?

States a specific verb ('Read'), resource ('Sponsored Display creatives'), and scope ('one page'), which cleanly separates it from the many other Amazon Ads readers in the sibling set. Within the SD family, creatives vs ad groups/campaigns/targets is unambiguous.

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?

Gives a real precondition — 'Requires Display eligibility' — which tells the agent when the call will apply. It does not, however, route the agent away from near-neighbors such as amazon_ads_get_sd_product_ads or amazon_ads_get_sb_ad_creatives, leaving the creative-vs-ad distinction to be inferred from the name.

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