Skip to main content
Glama

ads_list_sp_negative_targets

Read-only

List SP negative product targets Paginazione: all_pages=true di default, next_token per riprendere, complete/truncated per verificare la completezza.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ads_list_sp_negative_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
all_pagesNotrue = legge tutte le pagine; false = una sola pagina.
page_sizeNoRighe per pagina (intero).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
next_tokenNoToken di paginazione restituito dalla chiamata precedente.
profile_idNoAmazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost.
ad_group_idNoId ad group Amazon Ads (stringa numerica, da ads_list_*_ad_groups).
campaign_idNoId campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns).
state_filterNoFiltra per stato: array con ENABLED, PAUSED, ARCHIVED.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / all_pages
      Added value: +{
      +  "default": true,
      +  "description": "true = legge tutte le pagine; false = una sola pagina.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / next_token
      Added value: +{
      +  "description": "Token di paginazione restituito dalla chiamata precedente.",
      +  "type": "string"
      +}
    • addedInput schema / properties / page_size
      Added value: +{
      +  "default": 200,
      +  "description": "Righe per pagina (intero).",
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / state_filter
      Added value: +{
      +  "description": "Filtra per stato: array con ENABLED, PAUSED, ARCHIVED.",
      +  "items": {
      +    "enum": [
      +      "ENABLED",
      +      "PAUSED",
      +      "ARCHIVED"
      +    ],
      +    "type": "string"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / ad_group_id / description
      Added value: +"Id ad group Amazon Ads (stringa numerica, da ads_list_*_ad_groups)."
    • addedInput schema / properties / campaign_id / description
      Added value: +"Id campagna Amazon Ads (stringa numerica, da ads_list_*_campaigns)."
    • addedInput schema / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: all_pages defaults to true, next_token resumes a prior scan, and the response exposes complete/truncated fields for verifying completeness — a detail that matters given there is no output schema. It does not cover permissions or scope requirements (e.g. whether profile_id/account_id must be supplied).

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?

It is a single compact statement with the purpose front-loaded and no filler. The pagination clause is dense and mixes English and Italian, which slightly hurts scanability but nothing is redundant.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, no-required-parameter listing tool with no output schema, the description covers pagination and completeness signalling but leaves the filtering model unexplained — whether campaign_id/ad_group_id narrow the result and how account_id/profile_id resolve context is left entirely to the schema. Adequate to call correctly, but not fully self-sufficient.

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 every one of the 8 parameters is already documented in structured form, and the description merely restates all_pages, next_token and the complete/truncated fields without adding syntax, defaults-not-in-schema, or interaction rules. Baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb+resource: 'List SP negative product targets', which an agent can distinguish from the create/delete siblings and from ads_list_sp_targets or ads_list_sp_negative_keywords by the resource noun alone. It does not explicitly name a sibling or state the scope boundary (e.g. how it differs from listing positive targets), so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative tool is named; the agent must infer that this is the read counterpart to ads_create_sp_negative_targets / ads_delete_sp_negative_targets. The only guidance offered concerns pagination mechanics, not tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources