Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get sb negative targets

amazon_ads_get_sb_negative_targets
Read-onlyIdempotent

Retrieve Sponsored Brands negative targets from Amazon Ads. Manage your account exclusions by listing all enabled or archived targets, filtering results by campaign or ad group IDs.

Instructions

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

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.
nextTokenNoOpaque continuation token from the previous page for this same profile and filters. Omit on the first request.
adGroupIdsNoRestrict results to these ad group IDs, as decimal strings.
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 safety is covered. The description adds only the archived-inclusion note and pagination caveat; it says nothing about rate limits, result ordering, or what the page envelope looks like. Adequate but not rich.

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 clauses, both front-loaded with the essential fact (what is listed) followed by the pagination warning. No filler, nothing repeated from the schema.

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?

An output schema exists, so return-value explanation is unnecessary, and the pagination caveat plus archived note cover the key behavioral facts. The remaining gap is explicit routing among the many sibling listing tools, which the description 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 already carry documentation and this is the baseline case. The mention of 'cursor or offset' loosely maps to nextToken, but the description adds no 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?

The description gives a specific verb and resource ('List one page of Sponsored Brands negative targets'), and the 'Sponsored Brands' qualifier distinguishes it from amazon_ads_get_sd_negative_targets and amazon_ads_get_negative_targets. It does not explicitly name those siblings, so it falls short of the top mark.

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?

It tells the agent how to page ('Follow the returned cursor or offset; one page is not the whole inventory'), which is useful operational guidance. But it never states when to choose this over the SD negative targets or SB negative keywords tools, so the alternative-selection guidance is only implied by the entity name.

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