Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get sb ad creatives

amazon_ads_get_sb_ad_creatives
Read-onlyIdempotent

Retrieve all creative assets for a specific Sponsored Brands ad. Obtain detailed components like headlines, ASINs, brand logo, and image or video references using ad and account IDs.

Instructions

Read native Sponsored Brands creative versions for one ad: headline, ASINs, brand logo and image or video asset references. Resolve asset IDs with amazon_ads_get_creative_asset and ASINs with amazon_ads_get_product_metadata. Requires Brands eligibility; no retail scraping.

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>",
      "adId": "<adId>"
    },
    "name": "amazon_ads_get_sb_ad_creatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
adIdYesSponsored Brands ad ID in the selected profile.
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.
nextTokenNoOpaque continuation token from the previous page for this same profile and filters. Omit on the first request.
maxResultsNoMaximum entities in this page, up to 100. Follow the returned continuation value for the rest.

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.3/5.0
Behavior4/5

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

Annotations already declare this is read-only, idempotent, non-destructive, and open-world, so the description does not need to restate safety. It adds useful behavioral context beyond annotations: Brands eligibility is required, retail scraping is not used, and asset references need a follow-up resolution call.

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?

The description is three tight sentences: purpose first, dependency resolution second, eligibility/scope third. Every sentence adds useful information with no repeated or filler content.

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, full input-schema coverage, and rich annotations, the description supplies the remaining essentials: what creative data is returned, which dependency tools resolve references, and the Brands eligibility constraint. Nothing material for correct invocation is missing.

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 parameter semantics are primarily carried by the schema. The description only implies the ad-scoping meaning through 'for one ad' and does not add detail about accountId, pagination, or limits.

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: read Sponsored Brands creative versions for one ad, and enumerates the returned fields. It distinguishes this from SD creative tools by naming Sponsored Brands and from asset-listing tools by scoping to one ad and redirecting asset/ASIN resolution to dedicated siblings.

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 gives clear usage context by naming the required Brands eligibility and explicitly routing asset ID resolution to amazon_ads_get_creative_asset and ASIN resolution to amazon_ads_get_product_metadata. It stops short of explicitly contrasting with amazon_ads_get_sd_creatives or amazon_ads_list_creative_assets, so it is not full when/when-not guidance.

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