Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Bulk update products

bulk_update_products
Destructive

Update status, stock and price for many product records at once by applying a single patch to explicit IDs or a filtered selection.

Instructions

Bulk-update selected product records with a single patch (status, set/adjust stock, set/adjust price). Stock is whole units; price is major units - the stored price field value, not cents - and changes the default-currency price only; prices in additional currencies are left as they are. With allMatching the call is refused when more than 1000 products match: use start_bulk_update_products for that.

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": {
      "modelId": "<modelId>",
      "selection": "<selection>",
      "patch": "<patch>"
    },
    "name": "bulk_update_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYesSingle patch applied to every selected record
modelIdYesThe product model's id or slug (from list_models)
selectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / modelId / description
      Previous value: -"Product model id"New value: +"The product model's id or slug (from list_models)"
    • changedInput schema / properties / patch / properties / adjustPrice / description
      Previous value: -"Delta to price (minor units, +/-)"New value: +"Delta to price (major units of the default currency, +/-)"
    • removedInput schema / properties / patch / properties / adjustPrice / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / patch / properties / adjustPrice / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / patch / properties / adjustPrice / type
      Previous value: -"integer"New value: +"number"
    • changedInput schema / properties / patch / properties / setPrice / description
      Previous value: -"Set absolute price (minor units)"New value: +"Set absolute price (major units of the default currency - the stored price field value, 49.99 = $49.99)"
    • removedInput schema / properties / patch / properties / setPrice / maximum
      Removed value: -9007199254740991
    • changedInput schema / properties / patch / properties / setPrice / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / patch / properties / setPrice / type
      Previous value: -"integer"New value: +"number"
    • addedInput schema / properties / selection / properties / filter / properties / priceMax / description
      Added value: +"Major units - filters the stored price field directly"
    • addedInput schema / properties / selection / properties / filter / properties / priceMin / description
      Added value: +"Major units - filters the stored price field directly"
    • addedInput schema / required
      Added value: +[
      +  "modelId",
      +  "selection",
      +  "patch"
      +]
  2. First observedv0.73.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds non-obvious behavior on top: stock is whole units, price is major units of the stored field (not cents), only the default-currency price is changed while additional-currency prices are untouched, and there is a hard 1000-record ceiling that causes refusal. These are exactly the side effects an agent cannot infer from the annotations or schema.

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?

Three sentences, front-loaded with the action and then the two non-obvious constraints (units/currency scope, then the size ceiling). Dense but no wasted clauses; the em-dash-heavy second sentence is long but every clause carries a distinct fact.

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 nested parameters and no output schema, the description covers the critical unknowns: units, currency scope, and the refusal threshold with its alternative. It is silent on atomicity/partial-failure semantics and on how hasVariants or stockState filters interact with the patch, which keeps it from being fully complete.

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 67% and the description fills the important gaps: it explains that price values are major units mapped to the stored price field rather than cents, and it flags the multi-currency limitation that the schema's setPrice/adjustPrice descriptions omit. It does not clarify ids-vs-filter interaction beyond what the schema already says, so it stops short of full coverage.

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 (bulk-update), the resource (product records), and enumerates the patchable fields (status, set/adjust stock, set/adjust price) in the first sentence, which lets an agent distinguish it from bulk_delete_products and start_bulk_update_products without opening the schema.

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 an explicit routing rule: when allMatching exceeds 1000 matching products the call is refused, so use start_bulk_update_products instead. That is concrete when-to-use-which guidance, but there is no guidance on ids-vs-filter selection strategy or on when to prefer bulk_update_records.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools