Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete sales channel

delete_sales_channel
Destructive

Permanently delete a sales channel, unpublishing all its price lists and abandoning open carts; storefronts using its key are refused. Orders keep their original channel.

Instructions

Delete a sales channel and unpublish every price list from it. Its open carts are abandoned - activeCartCount in list_sales_channels / get_sales_channel says how many - and storefronts still sending its key are refused (BAD_USER_INPUT). Orders keep the channel they were placed through. Cannot be undone.

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": {
      "id": "<id>"
    },
    "name": "delete_sales_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe sales channel's id (from list_sales_channels)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.3/5.0
Behavior5/5

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

Goes far beyond the destructiveHint annotation by naming concrete cascading effects: price lists unpublished, open carts abandoned, storefront requests rejected with BAD_USER_INPUT, and orders retaining their channel. It also declares irreversibility ('Cannot be undone') and points to where to check impact (activeCartCount via list_sales_channels / get_sales_channel), which is exactly the pre-flight information an agent needs.

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?

Four short sentences, each delivering a distinct operational fact, with the destructive outcome and irreversibility front-loaded. No filler or restatement of the title.

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 one-parameter destructive tool with full schema coverage and no output schema, the description covers consequences, failure mode, data retention, and reversibility. Nothing material is left for the agent to guess before invoking it.

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 description coverage is 100% and the single 'id' parameter is already documented in the schema, including its provenance ('from list_sales_channels'). The description adds no format, validation, or lookup detail beyond that, so the baseline 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?

Opens with a specific verb and resource ('Delete a sales channel') and immediately extends it with the real scope ('unpublish every price list from it'), so an agent knows this is not a narrow channel-only record removal. That distinguishes it clearly from sibling mutations like update_sales_channel or delete_price_list.

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 gives strong decision-relevant context (open carts are abandoned, storefronts using the key get BAD_USER_INPUT, orders keep their channel) but never states when to choose this over an alternative such as detaching or unpublishing price lists individually, nor prerequisites like confirming activeCartCount first. Usage is implied by the warnings rather than spelled out as routing guidance.

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