Skip to main content
Glama

wc_update_order_status

Change a WooCommerce order status (e.g., processing to completed) and optionally add a private note. Refunds are not supported.

Instructions

Change a WooCommerce order's status (for example processing to completed). Cannot refund. Requires write mode.

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": {
      "id": "<id>",
      "status": "<status>"
    },
    "name": "wc_update_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
noteNoOptional private note added to the order
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the mutation nature, the write-mode requirement, and the refund limitation, which are real behavioral facts. It omits important traits for this operation — notably whether the status change triggers customer email notifications, whether it is reversible, and what a failed or partial call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action, then the restriction, then the prerequisite. Every sentence adds a distinct constraint and nothing is padded.

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 three-parameter mutation tool with no annotations and no output schema, the description covers the essential action and two hard constraints but leaves notable gaps: notification side effects, reversibility, and the meaning of the order identifier and private note. It is workable but not sufficient on its own.

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 coverage is only 33%: the 'note' parameter is documented in the schema but 'id' and 'status' are not, and 'status' is only covered by an enum. The description contributes a single transition example and says nothing about what 'id' refers to or what adding a 'note' does to the order, so it does not compensate for the low coverage.

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 — 'Change a WooCommerce order's status' — and adds a concrete transition example ('processing to completed') that pins down the operation. It is clearly distinguishable from read siblings like wc_get_order, though no sibling is named explicitly.

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?

Provides a prerequisite ('Requires write mode') and an explicit exclusion ('Cannot refund'), which tells the agent both when the call is permitted and what it must not be used for. It stops short of routing to an alternative tool for refunds, so the guidance is clear but not fully comparative.

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