Skip to main content
Glama

ads_update_sb_target_state

Destructive

Aggiorna lo stato (ENABLED|PAUSED|ARCHIVED) di uno o PIÙ product target Sponsored Brands. SINGOLA: target_id + state. BATCH: items=[{target_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_target_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoBatch: [{target_id, state}], max 25
stateNoStato: ENABLED, PAUSED oppure ARCHIVED (maiuscolo; ARCHIVED è irreversibile).
target_idNoId target Amazon Ads (da ads_list_*_targets).
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.
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 / state / description
      Added value: +"Stato: ENABLED, PAUSED oppure ARCHIVED (maiuscolo; ARCHIVED è irreversibile)."
    • addedInput schema / properties / items / items / properties / target_id / description
      Added value: +"Id target Amazon Ads (da ads_list_*_targets)."
    • 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)."
    • addedInput schema / properties / target_id / description
      Added value: +"Id target Amazon Ads (da ads_list_*_targets)."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds two useful facts beyond that — the 25-item batch cap and per-id outcome verification ("Esito verificato per-id") — but omits the preview/confirm_id two-step write flow and the irreversibility of ARCHIVED, both of which are significant for a destructive mutation and appear only in 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 clauses, purpose first, then the two modes, then the limit, then the outcome guarantee. Nothing repeats the name or title and no sentence is filler.

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

Completeness4/5

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

For a destructive 6-parameter mutation with no output schema, the description covers purpose, modes, batch ceiling, and result verification adequately, and the schema carries the rest at full coverage. The notable gap is the confirmation-token workflow, which an agent must know about to actually execute the write rather than just preview it.

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%, so the baseline is 3; the description earns above that by explaining the mutual exclusivity of the single (target_id + state) and batch (items) shapes and the 25-element ceiling, which the schema itself never states. It adds no meaning for account_id, profile_id, or confirm_id.

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

Purpose5/5

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

States a specific verb ("Aggiorna lo stato") and a precise resource ("product target Sponsored Brands") with the allowed state values inline, which separates it from ads_update_sb_keyword_state and ads_update_sb_target_bid without opening any schema.

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

Usage Guidelines4/5

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

Clearly routes the agent between the two invocation modes ("SINGOLA: target_id + state" vs "BATCH: items=[...], MAX 25"), which is real when-to-use guidance. It does not, however, state when to prefer this over alternatives such as pausing a whole ad group or campaign, nor any prerequisite 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