Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Start bulk update products

start_bulk_update_products
Destructive

Launch a background batch job to apply one status, stock, or price patch to every product matching a filter, intended when more than 1000 products match; track job progress separately.

Instructions

Start a background job that applies one patch (status, set/adjust stock, set/adjust price) to every product matching the filter. Use it instead of bulk_update_products when more than 1000 products match. Stock is whole units; price is major units of the default currency, and prices in additional currencies are left as they are. Returns the job at once; it runs in batches, so follow its progress with get_product_bulk_job. A model runs one job at a time: if one is already queued or running the start is refused - read it with get_product_bulk_job by modelId.

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>",
      "patch": "<patch>"
    },
    "name": "start_bulk_update_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYesSingle patch applied to every selected record
filterNoProducts to update; omit to update every product of the model
modelIdYesThe product model's id or slug (from list_models)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.146.2

TDQS

A4.7/5.0
Behavior4/5

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

Goes well beyond the destructiveHint=true annotation: it discloses that work happens asynchronously in batches, that the call returns the job immediately, that a per-model concurrency limit can cause a refusal, and that prices in additional currencies are left untouched. The only gap is that it does not say what happens to records that fail mid-batch or how to interpret the refused-start response beyond pointing at get_product_bulk_job.

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?

Front-loaded with the action and the alternative-selection rule, then unit semantics, then async/progress behavior, then the concurrency constraint. Every sentence carries information an agent needs; nothing is redundant with the title or schema.

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

Completeness5/5

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

For a destructive, nested-parameter, asynchronous tool with no output schema, the description covers what matters: the job model, immediate return, how to track progress, and the refusal condition. An agent has enough to invoke it correctly and handle the main failure mode.

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: stock is whole units, price is major units of the default currency, and non-default currencies are deliberately not modified - a caveat absent from the schema. It also clarifies that a single patch applies to every filtered record, reinforcing the nested patch/filter structure.

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?

Names a specific verb and resource ('start a background job that applies one patch ... to every product matching the filter') and enumerates the patch kinds (status, set/adjust stock, set/adjust price). It explicitly distinguishes itself from the sibling bulk_update_products, so an agent can pick between them without opening either schema.

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 an explicit selection rule: use this instead of bulk_update_products when more than 1000 products match. It also states the concurrency precondition (one job per model, start refused if one is queued or running) and directs the agent to get_product_bulk_job by modelId in that case, plus follow-up guidance for progress.

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