Skip to main content
Glama

ads_update_sb_keyword_state

Destructive

Aggiorna lo stato (ENABLED|PAUSED|ARCHIVED) di una o PIÙ keyword Sponsored Brands. SINGOLA: keyword_id + state. BATCH: items=[{keyword_id, state}], MAX 25. Esito verificato per-id.

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

Input Schema

NameRequiredDescriptionDefault
itemsNoBatch: [{keyword_id, state}], max 25
stateNoStato: ENABLED, PAUSED oppure ARCHIVED (maiuscolo; ARCHIVED è irreversibile).
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.
keyword_idNoId keyword Amazon Ads (da ads_list_*_keywords).
profile_idNoAmazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / items / items / properties / keyword_id / description
      Added value: +"Id keyword Amazon Ads (da ads_list_*_keywords)."
    • addedInput schema / properties / items / items / properties / state / description
      Added value: +"Stato: ENABLED, PAUSED oppure ARCHIVED (maiuscolo; ARCHIVED è irreversibile)."
    • addedInput schema / properties / keyword_id / description
      Added value: +"Id keyword Amazon Ads (da ads_list_*_keywords)."
    • addedInput schema / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
    • addedInput schema / properties / state / description
      Added value: +"Stato: ENABLED, PAUSED oppure ARCHIVED (maiuscolo; ARCHIVED è irreversibile)."
  2. First observed

TDQS

A3.5/5.0
Behavior3/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 write/destructive profile is known without the description. The description adds that the outcome is verified per-id ('Esito verificato per-id'), which hints at per-item result reporting, but it omits the confirm_id preview-then-execute requirement and any partial-failure semantics for a batch of up to 25. Useful context, but the highest-risk behavior (the confirmation gate) is left to the 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?

Four short, front-loaded fragments: action and valid states first, then the single form, then the batch form with its cap, then the result guarantee. No filler, no repetition of the title, and the mode labels make it scannable.

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 a destructive, batch-capable write tool with a confirmation token and no output schema, the description covers the core contract (states, both payload shapes, the 25-item cap, per-id outcome) but omits the mandatory preview/confirm round-trip and what a per-id failure looks like. Those gaps matter more here than for a read tool, so it is adequate rather than complete.

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% and the schema already documents keyword_id, state, items (with max 25), confirm_id, account_id and profile_id. The description mostly restates those parameters while organizing them into single vs batch modes, which is a modest framing gain rather than new semantic detail (e.g., no statement on whether keyword_id and items are mutually exclusive or how they interact). Baseline 3 is appropriate.

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 names a specific verb and resource ('Aggiorna lo stato ... di una o PIÙ keyword Sponsored Brands') and scopes it to SB, which separates it from the SP sibling. It also declares the two call shapes (single vs batch), so an agent knows exactly what the tool mutates. It stops short of naming any alternative tool explicitly, so it is clear but not sibling-differentiated in prose.

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?

It gives in-tool usage structure: 'SINGOLA: keyword_id + state' vs 'BATCH: items=[{keyword_id, state}], MAX 25', which is genuine when-to-use guidance for the two modes. However, it never mentions the preview/confirm two-step flow that the schema's confirm_id implies, nor when to prefer this over the SP equivalent or a bid/target update. Usage is implied by structure rather than stated as conditions.

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