Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete carts

delete_carts
Destructive

Permanently delete 1 to 100 carts with their analytics events, exclusive visitor sessions, and discount uses; the all-or-nothing call cannot be undone.

Instructions

Permanently delete 1 to 100 carts with their analytics events, the visitor sessions only they used and any discount use they held (the code's use count goes back down). All or nothing: an id that is not a cart of this workspace, or a cart already turned into an order (status ordered - anonymize the order instead), refuses the whole call and deletes nothing. Returns how many carts were deleted. 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": {
      "ids": "<ids>"
    },
    "name": "delete_carts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes1 to 100 cart ids (from list_carts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description goes well past them: it names every cascading artifact destroyed (events, sessions, discount-use with a decremented use count), declares all-or-nothing atomicity with exact refusal semantics, states the return value, and warns it cannot be undone. That is precisely the operational detail an agent needs before an irreversible bulk delete.

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 tightly packed sentences, front-loaded with the irreversible destructive action and scope, then the failure mode, then the return value. Every clause carries distinct operational information and none restates 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 single-parameter destructive bulk operation, the definition covers scope limits, cascade effects, atomicity, refusal conditions, the alternative path for ordered carts, irreversibility, and the return value. No output schema exists, and the description supplies the return shape itself, so nothing material is missing.

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% and the input schema already documents the 1–100 id array, so the baseline is 3. The description adds real meaning beyond it by requiring the ids be carts of this workspace and by warning that a single bad id invalidates the entire batch, which changes how an agent should prepare and validate the list.

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 (permanently delete) and resource (carts, 1 to 100) plus the full cascade scope: analytics events, visitor sessions only they used, and discount use. This is clearly distinguishable from the sibling delete_* tools that target unrelated resources such as media, pages, or records.

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 explicit preconditions and a when-not: any id that is not a cart of this workspace, or one already turned into an order, refuses the whole call, and it points to anonymizing the order as the alternative for ordered carts. The only gap is that the alternative action is not tied to a concrete sibling tool name, so the agent must still locate the anonymize tool itself.

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