Skip to main content
Glama
Amazon Ads MCP Server

Amazon Ads MCP Server

by get-mcp-ads

amazon ads get sd negative targets

amazon_ads_get_sd_negative_targets
Read-onlyIdempotent

Read a page of Sponsored Display negative targets for a specified advertising profile, using startIndex pagination to retrieve eligible records.

Instructions

Read one page of Sponsored Display negative targets. Requires Display eligibility. Pagination uses startIndex, not a cursor; full pages are conservatively marked partial. Creatives include native media references; these records are 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_sd_negative_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoMaximum entities in this page, up to 100.
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.
startIndexNoZero-based offset of the first entity. Use nextStartIndex from the previous page.

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

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description's added value is in the operational details: eligibility gating, offset-based rather than cursor pagination, and the non-obvious trait that full pages are conservatively flagged as partial. It also warns that these records carry no performance metrics, which prevents a common misinterpretation. Return shape and failure modes are 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences with the operation and eligibility constraint front-loaded, followed by pagination and scope caveats. The 'creatives include native media references' sentence is the weakest link for a negative-targets resource but still contributes disambiguation rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need no prose. Given that, the description covers the remaining agent-relevant gaps: eligibility precondition, pagination mechanics and its partial-page quirk, and the fact that these are targeting records rather than metrics. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already defines count, accountId, and startIndex, making 3 the baseline. The description earns a bump by clarifying that pagination is startIndex-based and not cursor-based and by explaining the partial-page marking behavior, which is semantics the schema alone does not convey.

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 opening sentence pairs a specific verb ('Read one page of') with a precisely qualified resource ('Sponsored Display negative targets'), which separates it from amazon_ads_get_sd_targets (positive) and amazon_ads_get_sb_negative_targets (Sponsored Brands). It stops short of explicitly naming those siblings, so differentiation is achieved through the resource qualifier rather than direct routing language.

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?

'Requires Display eligibility' is a genuine precondition that tells the agent when the call can succeed. However, there is no explicit statement of when to prefer this over positive-target or SB negative-target siblings, and no exclusions or error guidance; usage is only implied by the resource name.

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