Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get sb ads

amazon_ads_get_sb_ads
Read-onlyIdempotent

Read one page of Sponsored Brands ads for a profile, with optional filters for ad, campaign, and delivery state; use nextToken to retrieve subsequent pages.

Instructions

Read one page of Sponsored Brands ads. Requires Brands eligibility in this profile. Includes all states by default; follow nextToken. Configuration is not performance.

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

Input Schema

NameRequiredDescriptionDefault
adIdsNoRestrict results to these Sponsored Brands ad IDs, as decimal strings.
statesNoDelivery states to include. Defaults to every state, archived included.
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.
campaignIdsNoRestrict results to these campaign IDs, as decimal strings.

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. Changed4 schema fields changedv1.0.1
    • removedInput schema / properties / campaignIds / items / $ref
      Removed value: -"#/properties/adIds/items"
    • addedInput schema / properties / campaignIds / items / pattern
      Added value: +"^[1-9]\\d{0,19}$"
    • addedInput schema / properties / campaignIds / items / type
      Added value: +"string"
    • 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.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description is not obligated to restate safety. It adds non-obvious context the annotations lack: the Brands-eligibility gate, the all-states-by-default scope (archived included), and the paging contract.

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 with no filler; the core action and scope lead, then eligibility, then paging, then the reporting disambiguation. Every sentence carries distinct information.

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, return values need not be described, and the description covers scope, eligibility, defaults, and pagination. The one residual gap is not pointing to the reporting sibling explicitly, but nothing needed to invoke the tool 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 description coverage is 100%, so every parameter including adIds, campaignIds, states, nextToken and maxResults is already documented in the schema. The description's "includes all states by default" and "follow nextToken" merely restate schema defaults; baseline 3 applies.

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 ("Read one page of Sponsored Brands ads"), which cleanly separates it from sibling entity readers like amazon_ads_get_sb_campaigns and amazon_ads_get_sb_ad_groups. "Configuration is not performance" further rules out confusing it with amazon_ads_get_report.

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 prerequisite ("Requires Brands eligibility in this profile") and pagination instruction ("follow nextToken"), plus an implicit redirect to reporting tools via "Configuration is not performance." It does not name the specific alternative to use for performance data, so routing is only implied rather than explicit.

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