Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Bulk delete products

bulk_delete_products
Destructive

Permanently delete selected product records in bulk while skipping products referenced by open orders or page blocks; use filters or IDs, and start a bulk job when more than 1000 match.

Instructions

Bulk-delete selected product records permanently. A product still referenced by an open order or a page block is skipped rather than deleted; each entry of skipped carries its reason. With allMatching the call is refused when more than 1000 products match: use start_bulk_delete_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>"
    },
    "name": "bulk_delete_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelIdYesThe product model's id or slug (from list_models)
selectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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)"
    • 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"
      +]
  2. First observedv0.73.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds real behavioral detail beyond them: deletion is permanent, records still referenced by an open order or page block are skipped rather than deleted, each skipped entry carries a reason, and there is a hard 1000-record ceiling under allMatching. That is exactly the context an agent needs before invoking an irreversible operation.

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 sentences, front-loaded with the destructive action, then the skip semantics, then the limit and alternative. 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?

With no output schema, the description usefully explains the `skipped` return entries and their reasons, plus the refusal condition. It leaves minor gaps such as what a successful response contains (counts, job vs synchronous result), but is otherwise sufficient for a two-parameter destructive tool.

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 50% and the selection object is nested, so the schema carries most of the parameter meaning (ids, filter fields, allMatching). The description adds the important semantic that allMatching ignores ids and is capped at 1000 matches, but does not clarify the ids-vs-filter precedence or the skip behavior's interaction with filters. Baseline 3 is appropriate.

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 with scope ("Bulk-delete selected product records permanently") and explicitly distinguishes itself from the async sibling start_bulk_delete_products. An agent can tell which of the two bulk-delete tools to pick 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 Guidelines4/5

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

Gives a concrete routing rule: when allMatching would match more than 1000 products the call is refused and start_bulk_delete_products should be used instead. It also implies the synchronous use case (explicit selection). It does not cover when to prefer bulk_update_products or list_products first, but the key alternative is named with its triggering condition.

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