Frontman for WordPress

wc_delete_order_meta

Destructive

Deletes WooCommerce order metadata by key. Ask the user for confirmation before calling with confirm=true. Mirrors woocommerce-mcp-server method delete_order_meta 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>",
      "metaKey": "<metaKey>",
      "confirm": "<confirm>"
    },
    "name": "wc_delete_order_meta"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Must be true only after the user explicitly confirms deletion.
`metaKey`	Yes	The metadata key to delete.
`orderId`	Yes	The WooCommerce order ID.
`site_id`	Yes	The 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.

First observedNov 13, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds real value beyond that with a mandatory user-confirmation protocol and the authentication note that no WooCommerce REST API keys are needed. It stops short of saying what happens when the key does not exist.

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 short sentences with the action front-loaded and the safety-critical confirmation instruction prominent. No filler, though the authentication sentence is somewhat tangential to invocation and could be trimmed.

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

Completeness3/5

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

For a destructive tool with no output schema, the description covers the critical safety protocol and auth model. It omits return behavior, such as whether the call fails or reports success when the meta key is absent, which an agent would want to know before calling.

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 each parameter is already documented, giving a baseline of 3. The description adds only the 'by key' framing and the confirmation precondition for confirm, which is largely duplicative of the schema's own confirm description.

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 WooCommerce order metadata by key.' This clearly separates it from the customer-meta and product-meta deletion siblings by resource. It does not explicitly name alternatives, but the resource specificity carries the distinction well.

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?

Provides a clear procedural rule: ask the user for confirmation before calling with confirm=true. However, it gives no guidance on when to prefer this over siblings such as wc_update_order_meta (e.g., clearing a value instead of deleting the key) or when deletion is inappropriate.

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 tools Inspect

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.