Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads list creative assets

amazon_ads_list_creative_assets
Read-onlyIdempotent

Search the Amazon creative asset library for images, logos, and videos, returning download or playback URLs, sizes, and moderation metadata. Paginate results with nextToken using the same filters.

Instructions

Search the Amazon creative asset library: images, logos and videos, native download or playback URLs, sizes and moderation metadata. One page; continue with nextToken using the same filters. Uploaded assets are not proof of campaign use or delivery. Sponsored Products images come from amazon_ads_get_product_metadata instead.

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_list_creative_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoOptional free-text search over asset names and tags.
limitNoMaximum assets 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.
assetTypeNoRestrict results to images or videos.
nextTokenNoOpaque continuation token from the previous page for this same profile and filters. Omit on the first request.

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

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavior beyond them: single-page pagination with token continuation and a caveat that uploaded assets are not proof of campaign use or delivery. Reduces the risk of an agent treating library presence as delivery evidence; only return-shape detail is left to the output schema.

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?

Four short sentences, front-loaded with purpose, then pagination, then the caveat and alternative. Dense and mostly waste-free, though the compressed telegraphic phrasing ('native download or playback URLs, sizes and moderation metadata') reads as a list fragment rather than a sentence.

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?

For a read-only, paginated list tool with a full input schema, output schema, and annotations, the description covers the essentials: scope, pagination protocol, and the misleading-inference caveat. Minor gaps remain, such as whether unfiltered search spans all asset types or whether moderation status can be filtered.

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 every parameter (text, limit, accountId, assetType, nextToken) is already documented with constraints and enum values. The description only reinforces that nextToken must reuse 'the same filters'; it adds no search-syntax or matching semantics beyond the schema.

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 and resource ('Search the Amazon creative asset library') and enumerates what is returned: images, logos, videos, download/playback URLs, sizes, moderation metadata. It also routes an adjacent case away ('Sponsored Products images come from amazon_ads_get_product_metadata instead'), so the agent can separate it from siblings without opening schemas.

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 clear operating instructions: one page, continue with nextToken using the same filters, and an explicit alternative for Sponsored Products images. It does not, however, contrast itself with the sibling amazon_ads_get_creative_asset (single-asset fetch) or explain when searching by text vs assetType is preferred.

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