Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get campaign negative keywords

amazon_ads_get_campaign_negative_keywords
Read-onlyIdempotent

Retrieves one page of Sponsored Products campaign negative keywords, including paused and archived records by default, and returns a nextToken for pagination.

Instructions

Read one page of Amazon Sponsored Products campaign negative keywords, including paused and archived entities by default. Continue with nextToken until absent; one page is not an account total. These are configuration records, not performance metrics.

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

Input Schema

NameRequiredDescriptionDefault
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. 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

A4/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 safety is covered. The description adds genuinely non-obvious traits: the default inclusion of paused and archived entities and the fact that a single response is a page, not an account total. Return shape is left to the output schema.

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, zero filler, with the pagination caveat front-loaded alongside the resource statement. Every sentence carries distinct information (scope, pagination, category exclusion).

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 annotations covering safety, full schema coverage, and an output schema handling return values, the description covers the remaining gaps: pagination is mandatory, defaults include archived states, and this is configuration data. Only the explicit routing to a reporting sibling 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%, so state defaults, nextToken semantics, maxResults cap, and campaignIds filtering are already fully documented in the schema. The description restates the archived-by-default behavior but adds no new syntactic or format detail beyond it, so 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?

Names a specific verb and resource ('Read one page of Amazon Sponsored Products campaign negative keywords') with scoping detail (includes paused/archived). An agent can distinguish it from account-level get_negative_keywords and from get_campaign_negative_targets, though the sibling differentiation is implicit rather than stated.

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 clear when-to-use boundary ('configuration records, not performance metrics'), which steers the agent away from this tool for reporting queries, and instructs the nextToken continuation loop. It stops short of naming a specific alternative tool for performance data.

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