Woocommerce

Woo Get Order

woo_get_order

Read-onlyIdempotent

Fetch a single WooCommerce order by numeric ID. Returns full order details including line items, customer billing/shipping, payment method, totals, and current status.

Input Schema

Name	Required	Description
`id`	Yes	Order ID
`_apiKey`	Yes	WooCommerce consumer key
`_storeUrl`	Yes	Store URL (e.g., https://mystore.com)
`_apiSecret`	Yes	WooCommerce consumer secret

Output Schema

Name	Required	Description
`id`	No	Order ID
`total`	No	Order total
`number`	No	Order number
`status`	No	Order status
`billing`	No	Billing address details
`version`	No	Order version
`cart_tax`	No	Cart tax
`currency`	No	Currency code
`shipping`	No	Shipping address details
`order_key`	No	Order key
`parent_id`	No	Parent order ID
`total_tax`	No	Total tax
`line_items`	No	Order line items
`created_via`	No	Creation method
`customer_id`	No	Customer ID
`date_created`	No	Creation date in ISO format
`discount_tax`	No	Discount tax
`shipping_tax`	No	Shipping tax
`date_modified`	No	Last modified date in ISO format
`discount_total`	No	Discount total
`shipping_total`	No	Shipping total

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Single order object from WooCommerce",
+  "properties": {
+    "billing": {
+      "description": "Billing address details",
+      "type": "object"
+    },
+    "cart_tax": {
+      "description": "Cart tax",
+      "type": "string"
+    },
+    "created_via": {
+      "description": "Creation method",
+      "type": "string"
+    },
+    "currency": {
+      "description": "Currency code",
+      "type": "string"
+    },
+    "customer_id": {
+      "description": "Customer ID",
+      "type": "number"
+    },
+    "date_created": {
+      "description": "Creation date in ISO format",
+      "type": "string"
+    },
+    "date_modified": {
+      "description": "Last modified date in ISO format",
+      "type": "string"
+    },
+    "discount_tax": {
+      "description": "Discount tax",
+      "type": "string"
+    },
+    "discount_total": {
+      "description": "Discount total",
+      "type": "string"
+    },
+    "id": {
+      "description": "Order ID",
+      "type": "number"
+    },
+    "line_items": {
+      "description": "Order line items",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "number": {
+      "description": "Order number",
+      "type": "string"
+    },
+    "order_key": {
+      "description": "Order key",
+      "type": "string"
+    },
+    "parent_id": {
+      "description": "Parent order ID",
+      "type": "number"
+    },
+    "shipping": {
+      "description": "Shipping address details",
+      "type": "object"
+    },
+    "shipping_tax": {
+      "description": "Shipping tax",
+      "type": "string"
+    },
+    "shipping_total": {
+      "description": "Shipping total",
+      "type": "string"
+    },
+    "status": {
+      "description": "Order status",
+      "type": "string"
+    },
+    "total": {
+      "description": "Order total",
+      "type": "string"
+    },
+    "total_tax": {
+      "description": "Total tax",
+      "type": "string"
+    },
+    "version": {
+      "description": "Order version",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-woocommerce-api-key",
+    "_apiSecret": "your-woocommerce-api-secret",
+    "_storeUrl": "https://mystore.com",
+    "id": 456
+  }
+]

First observedApr 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description outlines the return fields (line items, customer billing/shipping, payment method, totals, status), adding value beyond annotations which already declare readOnlyHint, idempotentHint, etc. No contradiction with annotations.

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?

The description is two sentences, front-loaded with the main purpose. It is concise but could potentially be slightly more compact. No wasted words.

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

Completeness5/5

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

Given the tool's low complexity (fetch by ID, 4 clearly described parameters, output schema exists), the description provides complete context: what the tool does, input requirements, and return content.

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% with each parameter having a description. The tool description does not add meaning beyond the schema; it merely mentions 'numeric ID' which is already in schema (type: number). Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool description uses a specific verb ('Fetch') and identifies the resource ('single WooCommerce order by numeric ID'). It clearly distinguishes from sibling tools like 'woo_list_orders' (which lists multiple orders) and 'woo_get_product' (different resource).

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?

The description does not provide any guidance on when to use this tool versus alternatives, such as 'woo_list_orders' for fetching multiple orders. No when-to-use or when-not-to-use information is included.

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

All Woocommerce 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.