Skip to main content
Glama

bulk_update_listings

Destructive

Bulk listing attribute updates (title, bullet_point, any patch). A price patch (purchasable_offer) is subject to the ±50% limit on the last known price, like update_price. updates: [{sku, title?, bullets?: string[], patches?: [...], product_type?, validate_only?}]. product_type is optional: each SKU's product type is read from its listing (results[].product_type_used). Use when you need to update titles or bullets on multiple SKUs at once instead of calling update_listing one by one. Returns {total, ok, errors, results[]}. SAFETY: show preview and require confirm before sending.

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

Input Schema

NameRequiredDescriptionDefault
updatesYesArray di { sku, title?, patches? } con i soli campi da cambiare.
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. Changed7 schema fields changed
    • addedInput schema / properties / updates / description
      Added value: +"Array di { sku, title?, patches? } con i soli campi da cambiare."
    • addedInput schema / properties / updates / items / properties / bullets / description
      Added value: +"Bullet point del listing (array di stringhe, max 5)."
    • addedInput schema / properties / updates / items / properties / patches / description
      Added value: +"Modifiche da applicare: oggetto con i soli campi da cambiare."
    • addedInput schema / properties / updates / items / properties / product_type / description
      Added value: +"Product type Amazon, es. LUGGAGE (da get_product_types)."
    • addedInput schema / properties / updates / items / properties / sku / description
      Added value: +"SKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano)."
    • addedInput schema / properties / updates / items / properties / title / description
      Added value: +"Titolo prodotto (rispetta i limiti di caratteri della categoria)."
    • addedInput schema / properties / updates / items / properties / validate_only / description
      Added value: +"true = solo validazione Amazon, nessuna scrittura."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructive and open-world, and the description adds substantive behavior: a price patch is capped by the ±50% last-known-price limit, there is a two-phase preview/confirm flow with confirm_id, validate_only performs no write, and the response is {total, ok, errors, results[]}. This is real operational context an agent cannot get from the annotations alone.

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-loads the capability, then the price caveat, then usage, then return shape and the safety rule. The inline updates shape partially duplicates the schema and costs space, but it is short and the safety instruction lands at the end where it is noticed.

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 bulk mutation with no output schema, the description covers return shape, the confirmation workflow, and the price constraint. It omits practical limits an agent would want, such as a maximum SKU count per call or rate-limit behavior, which matters for a bulk tool.

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 adds meaning beyond it: product_type is optional because each SKU's type is read from its listing (surfaced as results[].product_type_used), and patches are described as partial-field objects. It does not clarify confirm_id or account_id interplay beyond what the schema says.

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 (bulk listing attribute updates) and enumerates the attributes covered (title, bullet_point, any patch). It explicitly contrasts with update_listing (one-by-one) and update_price, so an agent can place it among the siblings without opening schemas.

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 concrete selection rule: use this when updating titles or bullets across multiple SKUs rather than calling update_listing individually, and notes that price patches behave like update_price. It does not explicitly exclude the bulk price or inventory siblings, so the guidance is clear but not exhaustive.

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