Skip to main content
Glama

ads_update_sb_keyword_bid

Destructive

Aggiorna il BID di una o PIÙ keyword Sponsored Brands. È la leva per OTTIMIZZARE una campagna SB invece di spegnerla o strozzarne il budget. keyword_id si ottiene da ads_list_sb_keywords. SINGOLA: keyword_id + bid. BATCH (consigliato): items=[{keyword_id, bid}], MAX 25. Esito verificato per-id (read-after-write).

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

Input Schema

NameRequiredDescriptionDefault
bidNoBid in valuta del marketplace, es. 0.45.
itemsNoBatch: [{keyword_id, bid}], max 25
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 / bid / description
      Added value: +"Bid in valuta del marketplace, es. 0.45."
    • addedInput schema / properties / items / items / properties / bid / description
      Added value: +"Bid in valuta del marketplace, es. 0.45."
    • addedInput schema / properties / items / items / properties / keyword_id / description
      Added value: +"Id keyword Amazon Ads (da ads_list_*_keywords)."
    • 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."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds value beyond that by disclosing the per-id read-after-write verification ('Esito verificato per-id') and the hard batch ceiling of 25 items, both of which affect how an agent should call and trust the result. It does not spell out that existing bids are overwritten or that a preview/confirm_id round-trip is mandatory.

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?

Front-loaded with the action, then rationale, then the id source, then the two modes with caps labels and limits. Every sentence carries distinct information and there is no filler, despite the dense capitalization used for emphasis.

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 6-parameter destructive mutation with no output schema, the description covers modes, batch limit, id provenance and result verification. The remaining gaps — the preview/confirm_id write-confirmation flow and account_id/profile_id scoping — are documented in the schema, so nothing critical is missing, though one sentence on the confirm flow would make it self-sufficient.

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, but the description goes further by mapping parameters to two distinct calling patterns: 'SINGOLA: keyword_id + bid' and 'BATCH: items=[{keyword_id, bid}]', with the 25-item limit repeated. That mode-selection framing is meaning the flat schema does not convey on its own.

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 and resource ('Aggiorna il BID di una o PIÙ keyword Sponsored Brands') and scopes it to Sponsored Brands, which separates it from the Sponsored Products sibling ads_update_sp_keyword_bid. It also splits the tool into two explicit invocation modes (SINGOLA vs BATCH), so an agent knows exactly what operation it is calling.

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?

Gives a genuine when-to-use rationale: this is the lever to optimize an SB campaign 'invece di spegnerla o strozzarne il budget', implicitly pointing away from state/campaign-level tools. It also recommends the batch mode and names ads_list_sb_keywords as the source of keyword_id. It stops short of stating exclusions for the SP/SD bid siblings or the preview-confirm prerequisite in prose.

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