Woocommerce

Woo Get Product

woo_get_product

Read-onlyIdempotent

Fetch a single WooCommerce product by numeric ID. Returns full details including name, description, price, categories, attributes, and stock quantity.

Input Schema

Name	Required	Description
`id`	Yes	Product 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	Product ID
`sku`	No	Product SKU
`name`	No	Product name
`slug`	No	Product slug
`type`	No	Product type
`price`	No	Product price
`status`	No	Product status
`featured`	No	Whether product is featured
`permalink`	No	Product permalink
`tax_class`	No	Tax class
`sale_price`	No	Sale price
`tax_status`	No	Tax status
`description`	No	Product description
`total_sales`	No	Total sales count
`date_created`	No	Creation date in ISO format
`stock_status`	No	Stock status
`date_modified`	No	Last modified date in ISO format
`regular_price`	No	Regular price
`stock_quantity`	No	Stock quantity
`short_description`	No	Short product description
`catalog_visibility`	No	Catalog visibility

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Single product object from WooCommerce",
+  "properties": {
+    "catalog_visibility": {
+      "description": "Catalog visibility",
+      "type": "string"
+    },
+    "date_created": {
+      "description": "Creation date in ISO format",
+      "type": "string"
+    },
+    "date_modified": {
+      "description": "Last modified date in ISO format",
+      "type": "string"
+    },
+    "description": {
+      "description": "Product description",
+      "type": "string"
+    },
+    "featured": {
+      "description": "Whether product is featured",
+      "type": "boolean"
+    },
+    "id": {
+      "description": "Product ID",
+      "type": "number"
+    },
+    "name": {
+      "description": "Product name",
+      "type": "string"
+    },
+    "permalink": {
+      "description": "Product permalink",
+      "type": "string"
+    },
+    "price": {
+      "description": "Product price",
+      "type": "string"
+    },
+    "regular_price": {
+      "description": "Regular price",
+      "type": "string"
+    },
+    "sale_price": {
+      "description": "Sale price",
+      "type": "string"
+    },
+    "short_description": {
+      "description": "Short product description",
+      "type": "string"
+    },
+    "sku": {
+      "description": "Product SKU",
+      "type": "string"
+    },
+    "slug": {
+      "description": "Product slug",
+      "type": "string"
+    },
+    "status": {
+      "description": "Product status",
+      "type": "string"
+    },
+    "stock_quantity": {
+      "description": "Stock quantity",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "stock_status": {
+      "description": "Stock status",
+      "type": "string"
+    },
+    "tax_class": {
+      "description": "Tax class",
+      "type": "string"
+    },
+    "tax_status": {
+      "description": "Tax status",
+      "type": "string"
+    },
+    "total_sales": {
+      "description": "Total sales count",
+      "type": "number"
+    },
+    "type": {
+      "description": "Product type",
+      "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": 123
+  }
+]

First observedApr 22, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. Description adds no behavioral context beyond return contents, which is adequate but minimal given annotation coverage.

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?

Single sentence that front-loads the purpose and lists key return fields. No redundancy or wasted words.

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 simple get-by-ID tool with an output schema, the description covers the essential behavior and return fields. Does not explain error cases (e.g., invalid ID) but not required given annotations and schema.

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 coverage is 100% with descriptions for all parameters. The description adds no parameter-specific meaning beyond confirming 'numeric ID', so baseline score of 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?

Description clearly states 'Fetch a single WooCommerce product by numeric ID' with a specific verb and resource, and lists return fields (name, description, price, etc.), distinguishing it from sibling tools like woo_list_products which fetch multiple products.

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?

Implies usage for fetching one product by ID but lacks explicit guidance on when to avoid or alternatives. With siblings like woo_list_products, it could mention that this is for single products only.

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.