Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get creative asset

amazon_ads_get_creative_asset
Read-onlyIdempotent

Refresh a native Amazon image or video creative asset in a selected advertising profile and return every version and file without guessed URLs or cross-profile fallback.

Instructions

Refresh one native Amazon image or video asset in the selected profile. Returns every version and its files; no guessed URLs and no cross-profile fallback. Pass its native assetId from amazon_ads_list_creative_assets.

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>",
      "assetId": "<assetId>"
    },
    "name": "amazon_ads_get_creative_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesNative asset library ID, starting with amzn1.assetlibrary.
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.

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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description usefully adds that all versions and files are returned, that URLs are never guessed, and that there is no cross-profile fallback – good behavioral context beyond the annotations, though it says nothing about failure behavior when the asset is absent from the profile.

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?

Three short sentences, front-loaded with what the tool does, and every clause carries information: return shape, no guessed URLs, no fallback, and where to get the ID. Nothing is redundant with the title or with what the schema already states.

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?

It covers the action, the scope (one profile, one asset), the source of the required ID, the return payload (every version and its files), and an important boundary (no cross-profile fallback). With an output schema present and full schema parameter documentation, nothing an agent needs in order to call this correctly 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 coverage is 100% and both parameters are fully documented with patterns, so the schema does the heavy lifting. The description adds only mild value by stating the assetId is native and comes from amazon_ads_list_creative_assets, and that the profile is the 'selected' one – useful provenance but not format or constraint detail beyond the schema.

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?

It names a specific resource (one native Amazon image or video asset) and scopes it to a single profile, and the second sentence clarifies that this is a retrieval returning every version and its files. The verb 'Refresh' is slightly ambiguous for a read-only tool and could momentarily suggest re-uploading or regenerating the asset, which the sibling amazon_ads_list_creative_assets does not.

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 clearly routes the agent to amazon_ads_list_creative_assets as the source of the assetId, which is real usage guidance, and warns there is no cross-profile fallback so the profile must be the right one. It doesn't explicitly say when to call this versus just using the list response, but the single-asset lookup intent is clear.

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