Skip to main content
Glama

ads_update_sp_target_bid

Destructive

Aggiorna il bid di uno o PIÙ target SP (MANUAL ASIN/categoria o i 4 gruppi AUTO close/loose/substitutes/complements). Il target_id si ottiene da ads_list_sp_targets; è QUESTA (non ads_create_*) la via per modulare i bid dei gruppi auto su una campagna AUTO già esistente. SINGOLA: target_id + bid. BATCH (consigliato per molti target): items=[{target_id, bid}], ognuno con bid diverso, 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_sp_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.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description reinforces mutation semantics by specifying the batch cap of 25 and confirming a per-id result ('Esito verificato per-id'). However, it never mentions the preview/confirm_id two-step write flow that the schema implies, which is a significant behavioral trait for a destructive tool; adding that would raise the score.

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?

Front-loaded with purpose and scope, then mode-specific details, with no filler sentences. Capitalized emphasis words are slightly noisy but functional for an LLM reader; every clause carries information.

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, open-world mutation with no output schema, the description covers target-type scope, ID sourcing, batch limits, and per-id verification outcomes. The main omission is the confirm_id/preview prerequisite, which is only recoverable from the schema.

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 baseline is 3, but the description adds real meaning: it explains that target_id+bid and items are alternative modes, that each batch entry carries its own bid, and repeats the 25-item ceiling. It does not explain when account_id/profile_id matter beyond what the schema already states.

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 uno o PIÙ target SP') and enumerates exactly which target types are covered (MANUAL ASIN/categoria and the four AUTO groups). It explicitly distinguishes itself from ads_create_* tools, so an agent can route correctly without inspecting schemas.

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?

Gives the source of target_id (ads_list_sp_targets), an explicit negative directive ('non ads_create_*'), and a recommendation for batch use when many targets are involved. It also spells out the two call shapes (target_id+bid vs items=[...]) so the agent knows which usage applies.

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