Skip to main content
Glama

wc_create_product

Creates a simple WooCommerce product as a draft, requiring write mode, so you can stage new catalog items before publishing.

Instructions

Create a simple WooCommerce product as a draft. 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": {
      "name": "<name>",
      "regular_price": "<regular_price>"
    },
    "name": "wc_create_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNo
nameYes
descriptionNo
regular_priceYesPrice as a string, e.g. "19.99"
stock_quantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose two valuable facts the schema cannot: the product is created as a draft (not published) and write mode is required. It omits SKU uniqueness behavior, validation failure modes, and what the response contains, leaving meaningful gaps for a mutation tool.

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?

Two short sentences, zero filler, with the core action and its output state front-loaded ahead of the precondition. Nothing could be removed without losing information.

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 five-parameter mutation tool with no annotations and no output schema, the description supplies the two most decision-relevant facts (draft state, write mode) but leaves parameter guidance and return behavior unaddressed. Adequate as a minimum, not complete.

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 description coverage is only 20% (just regular_price), with five parameters total, yet the description says nothing about name, sku, description, or stock_quantity semantics. It does not compensate for the low coverage, so an agent learns nothing about optional field behavior or uniqueness constraints for sku.

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 simple WooCommerce product') plus the resulting state ('as a draft'), which is enough to distinguish it from generic post-creation siblings like wp_create_post. It stops short of explicitly naming which sibling to use for more complex product types.

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

Usage Guidelines3/5

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

'Requires write mode' is a genuine prerequisite that tells the agent a precondition must be met before calling. There is no guidance on when to prefer this over wc_update_product or which sibling handles variations/complex products, so usage is only implied.

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