Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WooCommerce: Delete order

woocommerce_delete_order
Destructive

Permanently delete a WooCommerce order or move it to trash by specifying the site and order ID, giving you control over unwanted or test orders.

Instructions

[UNIFIED] Delete or trash a WooCommerce order. Can permanently delete or move to trash.

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": {
      "site": "<site>",
      "order_id": "<order_id>"
    },
    "name": "woocommerce_delete_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
forceNo
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally. The description adds the meaningful distinction that the call can either trash or permanently remove the order, but it never says which mode is irreversible or what happens to order line items/metadata. No auth or side-effect details beyond the annotations.

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?

Two short sentences with no filler and the core action front-loaded. The second sentence is somewhat redundant with the first ('trash' already implies the non-permanent branch) but adds modest clarification.

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

Completeness2/5

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

For a destructive, two-mode tool with zero schema description coverage and no output schema, the definition should map each parameter to its effect and state irreversibility. It leaves the force/trash relationship and the site parameter entirely unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must carry the load. It gestures at a trash-vs-permanent behavior but never attributes it to the 'force' parameter, and gives no meaning for 'site' or 'order_id' beyond their names. An agent still cannot tell from the text that force=true means permanent deletion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Delete or trash a WooCommerce order,' which clearly separates it from create/get/update-order siblings by operation. It doesn't explicitly name an alternative, but the verb+resource pairing is unambiguous.

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 implies two usage modes (permanent delete vs. move to trash) but never says when to choose each, nor mentions prerequisites or that the operation cannot be undone. Guidance is implied rather than stated.

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