Skip to main content
Glama

ads_create_sp_negative_targets

Destructive

Create SP negative product targets. Each: { campaign_id, ad_group_id, asin (or raw expression) }.

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": {
      "targets": "<targets>"
    },
    "name": "ads_create_sp_negative_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetsYesTarget da creare: array di oggetti (campi nella descrizione del tool).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
confirm_idNoToken di conferma ritornato dall'anteprima. Ripassa lo STESSO payload + confirm_id per eseguire davvero la scrittura.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / targets / description
      Added value: +"Target da creare: array di oggetti (campi nella descrizione del tool)."
  2. First observed

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing about the confirmation-token workflow, whether the write is idempotent, or what happens if the payload differs from the previewed one — the most important behavior for a destructive write.

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 short sentences, front-loaded with the action and then the item shape; nothing is wasted. Terseness here comes at the cost of omitting the confirm flow rather than from good editing, but the structure itself is efficient.

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

Completeness2/5

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

This is a destructive, open-world write with no output schema, and the description omits the two-step preview/confirm_id protocol that the schema hints at. An agent reading only the description could attempt a write without the confirmation token and fail, so the definition is not complete for the tool's complexity.

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 coverage is 100%, but the schema's own description of the 'targets' array explicitly delegates the item fields to the tool description, so the description is load-bearing. It names campaign_id, ad_group_id and asin (or raw expression), which meaningfully defines the item shape. It does not clarify the 'raw expression' syntax or explain account_id/confirm_id semantics.

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 states a specific verb and resource ('Create SP negative product targets'), and the word 'negative' distinguishes it from the sibling ads_create_sp_product_targets. It is clear what the tool does, though it does not explicitly name the alternative tool for non-negative targets.

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 mention of prerequisites. Critically, the schema reveals a preview/confirm_id two-step write flow, but the description never tells the agent that a preview must precede the actual write.

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