Skip to main content
Glama

ads_update_sb_target_bid

Destructive

Aggiorna il BID di uno o PIÙ product target Sponsored Brands. Insieme a ads_update_sb_keyword_bid e ai moltiplicatori per posizionamento di ads_update_sb_campaign è il modo per OTTIMIZZARE SB (invece di limitarsi a spegnere o tagliare il budget). target_id da ads_list_sb_targets. SINGOLA: target_id + bid. BATCH: items=[{target_id, bid}], 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_bid"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidNoBid in valuta del marketplace, es. 0.45.
itemsNoBatch: [{target_id, bid}], max 25
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 / 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 / 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 / target_id / description
      Added value: +"Id target Amazon Ads (da ads_list_*_targets)."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the mutation risk is covered structurally. The description adds genuinely useful behavior beyond that: the hard cap of 25 items per batch and the promise of per-id verification of the outcome ('Esito verificato per-id'), which tells the agent partial failures are reported individually. It does not spell out that writes require a preview+confirm_id round-trip, but the schema does.

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?

Very dense and front-loaded: verb+resource first, then alternatives, then ID source, then the two modes, then the outcome guarantee. The telegraphic caps and the short parenthetical motivational clause are justified by routing value, though the style is compressed enough to read as notes rather than prose.

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

Completeness5/5

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

For a 6-parameter mutation tool with no output schema, the definition covers everything an agent needs to call it correctly: which resource, where IDs come from, single vs. batch shape, batch limit, and that results are verified per id. The remaining parameters (account_id, profile_id, confirm_id) are fully documented in the schema, so nothing essential is missing.

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 would be 3, but the description adds meaning the schema cannot: it establishes the two mutually exclusive calling shapes (target_id + bid vs. items=[...]) and the origin of target_id, which matters because the schema marks zero parameters as required and would otherwise let an agent pass both forms or neither.

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 (update) and resource (Sponsored Brands product target bid) and immediately distinguishes itself from the two closest siblings: ads_update_sb_keyword_bid (keyword bids) and ads_update_sb_campaign (placement multipliers). An agent can pick the right tool 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 Guidelines5/5

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

Frames the use case explicitly ('il modo per OTTIMIZZARE SB invece di limitarsi a spegnere o tagliare il budget'), names the complementary alternatives, points to ads_list_sb_targets as the ID source, and separates the SINGOLA and BATCH invocation patterns. The only minor omission is an explicit when-not rule, but the positive routing is unambiguous.

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