Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Remove price list entries

remove_price_list_entries
Destructive

Remove fixed prices from a price list by product or variant key, optionally per currency; affected products fall back to catalogue price minus the list's percentOff.

Instructions

Remove up to 1000 fixed prices from a price list by key: recordId alone for a product without variants, recordId + variantKey for one variant of a product with variants; currency limits a key to that currency's row, without it every currency's row goes. Those products then fall back to the catalogue price minus the list's percentOff. Returns how many were removed; a key with no entry removes nothing.

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": {
      "priceListId": "<priceListId>",
      "keys": "<keys>"
    },
    "name": "remove_price_list_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYesUp to 1000 product / variant keys whose fixed price to remove
priceListIdYesThe price list's id (from list_price_lists)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only flag it as destructive; the description goes further by disclosing the post-removal fallback (catalogue price minus percentOff), that a key with no entry is a silent no-op, and that omission of currency wipes every currency's row. Those are exactly the consequences an agent needs before calling a destructive tool.

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-loaded with the verb and resource, and every clause carries information (key shapes, currency scope, fallback, return value, no-op). The single dense block is efficient but could be broken into shorter sentences for faster scanning.

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 two-parameter destructive tool with no output schema, the description covers the key formats, currency behavior, side effects, return value, and no-op case. Nothing material is missing for correct invocation.

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% and the schema descriptions already spell out recordId, variantKey, and currency semantics, so the description largely restates them. It adds the aggregate 1000-item ceiling context but little else beyond the structured fields, so baseline 3 applies.

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 (Remove), resource (fixed prices from a price list), and scope (up to 1000, by key). The key-form rules and the implicit contrast with set_price_list_entries make the operation unambiguous 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 Guidelines3/5

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

The description explains the key formats and the currency-scoping condition, which implies when a key is valid, but it never states when to choose this tool over siblings such as set_price_list_entries or delete_price_list. Usage is inferable rather than explicit.

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