Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_delete_order

Destructive

Deletes a WooCommerce order. Ask the user for confirmation before calling with confirm=true. Mirrors woocommerce-mcp-server method delete_order using local WordPress authentication; no WooCommerce REST API keys are required.

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_id": "<site_id>",
      "orderId": "<orderId>",
      "confirm": "<confirm>"
    },
    "name": "wc_delete_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoIf true, permanently delete where WooCommerce supports forced deletion.
confirmYesMust be true only after the user explicitly confirms this WooCommerce mutation.
orderIdYesThe order ID.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds the human-confirmation gate and the authentication model (local WordPress auth, no REST keys). It does not explain what 'force' defaults to, whether an unforced delete trashes versus removes the order, or what happens to line items and refunds.

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?

Three sentences, front-loaded with the action and the confirmation rule, with no filler. The final sentence about mirroring the upstream method and auth requirements is slightly tangential but still gives the agent relevant context about credentials.

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?

For a destructive two-mode delete with full schema coverage and strong annotations, the definition covers the essentials: what it deletes, the confirmation requirement, and the auth model. The notable remaining gap is the trash-versus-permanent distinction controlled by force, which the description leaves entirely to the schema.

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%, so all four parameters including confirm, force, orderId and site_id are already documented in the schema. The description reinforces the confirm semantics but adds no new meaning about orderId or force beyond what the schema states. Baseline 3 applies.

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 ('Deletes a WooCommerce order'), which cleanly separates it from siblings like wc_delete_order_note, wc_delete_order_refund, and wc_delete_order_meta that operate on sub-resources. It does not explicitly name or contrast those siblings, keeping it short of a 5.

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 operational prerequisite: ask the user for confirmation before calling with confirm=true, which directly shapes how the agent should sequence the call. It offers no guidance on when to delete versus alternatives such as updating status or issuing a refund, so there are no explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources