Skip to main content
Glama

woo_add_order_note

Add a private or customer-facing note to a WooCommerce order using the site, order ID, and note content.

Instructions

Add a note to an order

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": "<site>",
      "id": "<id>",
      "note": "<note>"
    },
    "name": "woo_add_order_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrder ID
noteYesNote content
siteYesSite id (see list_sites)
customer_noteNoCustomer-facing note, emailed to the customer (default false = private)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.14.0
    • removedInput schema / properties / customer_note / default
      Removed value: -false
    • changedInput schema / properties / customer_note / description
      Previous value: -"Send to customer"New value: +"Customer-facing note, emailed to the customer (default false = private)"
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "note"
      -]New value: +[
      +  "site",
      +  "id",
      +  "note"
      +]
  3. First observedv2.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about side effects. It omits that a note may be emailed to the customer, that notes are private by default, and what permissions or failure modes apply to this mutation.

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

Conciseness3/5

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

The single short sentence is front-loaded and free of padding, but its brevity borders on under-specification rather than genuine conciseness — nothing about behavior or prerequisites is included.

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

Completeness2/5

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

This is a four-parameter mutation tool with no annotations and no output schema, which raises the disclosure bar considerably. A one-line description leaves out side effects, the customer-email implication, and expected results, so it is not sufficient for the tool's complexity.

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 the parameters (id, note, site, customer_note) are already documented in the schema, including the customer-facing/email semantics of customer_note. The description adds no meaning beyond that, which is the expected baseline.

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 states a specific verb and resource ('Add a note to an order'), so the agent can tell this is a write operation on order notes rather than the read-only sibling woo_get_order_notes. It offers no explicit sibling differentiation, but the purpose itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives such as woo_get_order_notes or other order-mutation tools, and no stated prerequisites (e.g., the order must exist, a valid site id is required). The agent must infer all usage conditions.

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

Deploy Server

Other Tools