Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_delete_order_note

Destructive

Deletes a note from a WooCommerce order. Ask the user for confirmation before calling with confirm=true. Mirrors woocommerce-mcp-server method delete_order_note 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>",
      "noteId": "<noteId>",
      "confirm": "<confirm>"
    },
    "name": "wc_delete_order_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoIf true, permanently delete where WooCommerce supports forced deletion.
noteIdYesThe order note ID.
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.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is known. The description adds real value beyond that: a mandatory user-confirmation step and the fact that it authenticates via local WordPress credentials rather than REST API keys. It stops short of saying what is returned after deletion.

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 confirmation rule second. The final sentence about mirroring the server method and local auth is slightly meta but carries the useful authentication fact.

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 five-parameter tool with full schema coverage and rich annotations, the description covers action, safety gate, and auth model. The only gap is the post-deletion result, which matters less since no output schema is declared and the operation is a simple delete.

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 five parameters are already documented, including confirm and site_id guidance. The description only restates the confirm gate and adds nothing about force or noteId semantics, so the 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?

The description opens with a specific verb and resource: deletes a note from a WooCommerce order. That is clearly distinct from siblings such as wc_delete_order or wc_delete_order_meta, though it never explicitly names those siblings to route the agent.

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?

It gives a procedural rule ('Ask the user for confirmation before calling with confirm=true'), which covers the safety gate but not when to choose this tool over wc_get_order_notes or wc_delete_order. The usage context is implied rather than contrasted with alternatives.

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