Skip to main content
Glama

ads_create_sp_negative_keywords

Create SP negative keywords

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": {
      "negatives": "<negatives>"
    },
    "name": "ads_create_sp_negative_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
negativesYesKeyword negative da creare: array di { campaignId, adGroupId?, keywordText, matchType } (matchType NEGATIVE_EXACT o NEGATIVE_PHRASE).
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 / negatives / description
      Added value: +"Keyword negative da creare: array di { campaignId, adGroupId?, keywordText, matchType } (matchType NEGATIVE_EXACT o NEGATIVE_PHRASE)."
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it never mentions the two-step preview/confirm_id execution model, whether duplicates are rejected, or that account_id is token-dependent, all of which are behaviors an agent should know before invoking a write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Three words with zero waste, but this is terseness rather than disciplined conciseness; there is no structure, no front-loaded scope statement, and nothing that earns the space it leaves empty.

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?

For a mutation tool that requires a confirm round-trip and optional account scoping, the description is far too thin. The schema does document confirm_id and account_id, but the definition as a whole leaves an agent with no framing for when this call is appropriate or what it affects.

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%, with detailed Italian descriptions for negatives, account_id and confirm_id, so the schema carries the parameter meaning. The description contributes nothing additional, which is the expected baseline when coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create SP negative keywords" names a specific verb and resource, but it is essentially a restatement of the tool name and title. It gives no signal about how this differs from nearby siblings such as ads_create_sp_negative_targets or ads_create_sp_keywords.

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 guidance, no mention of prerequisites, and no pointer to alternatives like ads_create_sp_negative_targets for product targets. The agent must infer from the name alone that this is the keyword-level negative tool.

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