Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get sb negative keywords

amazon_ads_get_sb_negative_keywords
Read-onlyIdempotent

Lists one page of Sponsored Brands negative keywords, including archived ones, so you can page through the full inventory using cursor or offset.

Instructions

List one page of Sponsored Brands negative 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_negative_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entities in this page, up to 100.
statesNoStates to include, in Amazon's lower case. Negative criteria are enabled or archived.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so safety is covered. The description adds a genuinely useful caveat that results are paginated and incomplete per call, but does not cover return shape or anything about archived-entity semantics beyond what the schema default states.

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?

Two tight sentences with the resource statement front-loaded and the pagination warning second; no filler. Slight redundancy with the schema's default of enabled+archived for the 'including archived entities' clause keeps it from a 5.

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 a full output schema and 100% parameter coverage, the description covers what it must: what list this is and that results are paged. The remaining gap is disambiguation from the large set of sibling negative-keyword/target tools, which it leaves implicit.

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 fully documented in the schema (limit, states, accountId, adGroupIds, startIndex, campaignIds). The description adds nothing parameter-specific beyond the pagination hint, so baseline 3 is appropriate.

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?

Specific verb (List) and resource (Sponsored Brands negative keywords) with scope ('one page', 'including archived entities'). The 'Sponsored Brands' qualifier implicitly distinguishes it from sibling get_negative_keywords and get_sd_negative_targets, though it never names them explicitly.

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 useful operational context, but it gives no when-to-use/when-not guidance nor names any alternative among the many sibling list tools. Usage is only implied by the tool being a filtered lister.

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