Skip to main content
Glama

update_price

Destructive

Update price for a SKU

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sku": "<sku>",
      "price": "<price>"
    },
    "name": "update_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesSKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano).
priceYesPrezzo di vendita in valuta del marketplace, es. 19.90.
currencyNoCodice valuta ISO 4217, es. EUR.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / currency / description
      Added value: +"Codice valuta ISO 4217, es. EUR."
    • addedInput schema / properties / price / description
      Added value: +"Prezzo di vendita in valuta del marketplace, es. 19.90."
    • addedInput schema / properties / sku / description
      Added value: +"SKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano)."
  2. First observed

TDQS

C2.8/5.0
Behavior2/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 safety profile is covered. The description adds nothing beyond that: it never mentions that the change is live on the marketplace, that it is destructive, or that a confirm_id from a preview must be replayed to actually commit the write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but at four words it is under-specified rather than concise. For a destructive five-parameter write tool it leaves the agent with no structure to act on beyond the name.

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

Completeness2/5

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

With five parameters, destructive semantics, and a mandatory two-step preview-then-confirm flow, the description should at minimum flag that the first call is a preview and that the same payload plus confirm_id performs the write. None of that is present, and there is no output schema to compensate.

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%, so each parameter including the preview/confirm semantics of confirm_id is documented in the schema. The description contributes no additional meaning, which is the baseline 3 when the schema does the heavy lifting.

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?

"Update price for a SKU" states a specific verb and resource, so an agent immediately knows this mutates a single SKU's price. It does not differentiate from nearby siblings such as bulk_update_prices or woo_update_price, leaving scope ambiguity when multiple price tools are available.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over bulk_update_prices or woo_update_price, nor any statement of prerequisites or exclusions. The only usage-critical fact, that a preview/confirm round-trip is needed, is absent from the description entirely.

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