wordpress-mcp

woo_create_product

Create a WooCommerce product for a WordPress site through MCP, specifying name, type, price, stock, categories, images, and metadata.

Instructions

Create a WooCommerce product

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>",
      "name": "<name>"
    },
    "name": "woo_create_product"
  }
}

Input Schema

Name	Required	Description	Default
`sku`	No
`name`	Yes	Product name
`site`	Yes	Site id (see list_sites)
`tags`	No
`type`	No		simple
`images`	No
`status`	No		publish
`meta_data`	No
`attributes`	No
`categories`	No
`sale_price`	No
`description`	No
`manage_stock`	No
`stock_status`	No		instock
`regular_price`	No
`stock_quantity`	No
`short_description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.4.0Oct 1, 2026

addedInput schema / properties / site

Added value: +{
+  "description": "Site id (see list_sites)",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "name"
-]New value: +[
+  "site",
+  "name"
+]

First observedv2.0.0Jun 21, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not mention that the default status is 'publish' (product goes live immediately), what permissions/authentication are needed, or which fields are required. 'Create' at least correctly signals a mutation, but that is all.

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 sentence is maximally concise and front-loaded, but for a 17-parameter tool this brevity is under-specification rather than efficiency. It earns no waste but also conveys almost nothing.

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

Completeness1/5

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

A 17-param mutation tool with 12% schema coverage, no annotations, and no output schema. The description should compensate heavily and instead provides five words, leaving required-field usage, ID conventions, and the publish-by-default side effect unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

17 parameters with only 12% schema description coverage, and the description adds zero parameter meaning. Critical items like the 'site' param's dependency on list_sites, numeric ID arrays for tags/images/categories, and enum semantics for 'type' are left entirely undocumented.

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 ('Create a WooCommerce product'), so an agent can tell it apart from unrelated tools like wp_create_post or woo_create_coupon. However it does nothing to distinguish it from close siblings such as woo_create_variation or woo_update_product beyond the obvious create verb.

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?

No guidance on when to use this versus alternatives, no prerequisites, no mention of the required list_sites step needed for the 'site' parameter. The agent must infer everything from the schema.

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

Deploy Server