Skip to main content
Glama

bulk_update_prices

Destructive

ACTION. Updates the price of several SKUs in one call ([{sku, price}]). Preview first, apply only after explicit user approval; prices are capped at ±50% vs the current one. Returns per-SKU results.

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": {
      "updates": "<updates>"
    },
    "name": "bulk_update_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYesArray di { sku, price } (price in valuta del marketplace, es. 19.90).
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. Changed1 schema field changed
    • addedInput schema / properties / updates / description
      Added value: +"Array di { sku, price } (price in valuta del marketplace, es. 19.90)."
  2. First observed

TDQS

A4/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 description's job is to add detail — and it does: a two-phase preview/confirm workflow, a hard ±50% price cap versus current price, and per-SKU result reporting. It does not describe what happens on partial failure across SKUs or whether partial application is possible, which would complete the mutation profile.

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?

Three short sentences, front-loaded with a mutation signal ('ACTION.') and followed immediately by scope, workflow constraint, and return behavior. No filler; every clause carries operational 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 3-parameter mutation tool with full schema coverage and no output schema, the description covers purpose, mandatory preview/approval flow, a price constraint, and return granularity. The only gap is multi-account/marketplace scoping (account_id), which is left entirely to the schema.

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 coverage is 100%, so all three parameters (updates, account_id, confirm_id) are already documented in the schema. The description adds the ±50% cap, which is meaningful semantics for the price field beyond the schema, but adds nothing about account_id scoping or confirm_id handling. Baseline 3 is appropriate given the schema does most of the work.

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?

States a specific verb and resource — 'Updates the price of several SKUs in one call' — and includes the payload shape ([{sku, price}]), which implicitly distinguishes it from single-SKU price update siblings. It does not name any sibling explicitly (e.g., update_price vs woo_update_price), so the differentiation is left partly to inference.

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 clear procedural rule: 'Preview first, apply only after explicit user approval,' which tells the agent the required call sequence. It lacks guidance on when to prefer this over the single-SKU price tools or how to choose among marketplace/account scopes, but the core usage constraint is explicit.

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