Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get sb keywords

amazon_ads_get_sb_keywords
Read-onlyIdempotent

Lists one page of Sponsored Brands keywords, including archived entities, and returns a cursor or offset so you can page through the full keyword inventory.

Instructions

List one page of Sponsored Brands keywords, including archived entities. Follow the returned cursor or offset; one page is not the whole inventory.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entities in this page, up to 100.
statesNoStates to include, in Amazon's lower case. Defaults to every state.
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.
adGroupIdsNoRestrict results to these ad group IDs, as decimal strings.
startIndexNoZero-based offset of the first entity. Use nextStartIndex from the previous page.
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 / adGroupIds / items / $ref
      Removed value: -"#/properties/campaignIds/items"
    • addedInput schema / properties / adGroupIds / items / pattern
      Added value: +"^[1-9]\\d{0,19}$"
    • addedInput schema / properties / adGroupIds / 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

A3.6/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 adds the meaningful behavioral fact that results are paginated and partial, plus archived inclusion. It says nothing about permission/profile requirements or result ordering, so it adds context but not rich detail.

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?

Two short sentences with zero waste. The resource and scope come first, followed immediately by the pagination caveat.

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 full schema coverage and an output schema covering return values, the description supplies the essential facts: what is listed, archived inclusion, and that pagination must be continued. The only gap is differentiation from sibling keyword/target listing tools.

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 all six parameters are already documented, including limit, startIndex, states, and the ID filters. The description only alludes to the cursor/offset (startIndex) concept and adds no syntax or constraint detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('List one page of Sponsored Brands keywords') and adds the useful scope detail that archived entities are included. It does not explicitly distinguish itself from the generic amazon_ads_get_keywords or amazon_ads_get_sb_negative_keywords siblings, so the SB-vs-generic boundary is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives pagination guidance ('follow the returned cursor or offset; one page is not the whole inventory'), which is real usage advice. It offers no when-to-use or when-not-to-use versus the many sibling list tools (e.g., amazon_ads_get_keywords, amazon_ads_get_sb_targets), leaving that choice to inference.

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