Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_update_order

Destructive

Updates a WooCommerce order. Ask the user for confirmation before calling with confirm=true. Mirrors woocommerce-mcp-server method update_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>",
      "orderData": "<orderData>",
      "confirm": "<confirm>"
    },
    "name": "wc_update_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
orderDataYesWooCommerce order fields to update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 genuinely new context: the explicit user-confirmation gate and the fact that it uses local WordPress authentication with no WooCommerce REST API keys required.

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, front-loaded with the action and the confirmation requirement. No filler, though the authentication sentence is secondary detail placed after the critical safety instruction.

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 mutation with a nested orderData object whose properties are empty and open-ended, the description never indicates which order fields are updatable or what the response contains. With no output schema, that leaves a meaningful gap for an agent constructing the payload.

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 are already documented, including the confirm semantics and the site_id/list_sites instruction. The description restates the confirmation rule but adds no new meaning about orderData or orderId beyond the schema.

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 ("Updates a WooCommerce order"), which clearly separates it from wc_create_order and wc_delete_order. It does not explicitly distinguish itself from the closely related wc_update_order_meta, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete precondition for the confirm flag (ask the user first, then pass confirm=true), which is real usage guidance. However, it offers no guidance on when to choose this tool over siblings like wc_update_order_meta or wc_update_order_note.

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