Skip to main content
Glama

WooCommerce: Create product

woocommerce_create_product

Create a new WooCommerce product as simple or variable, setting price, stock, categories, tags, descriptions, and meta data in one call.

Instructions

[UNIFIED] Create a new WooCommerce product. Supports simple and variable products with pricing, inventory, categories, tags, descriptions, and WooCommerce meta_data.

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": "woocommerce_create_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
siteYes
tagsNo
typeNosimple
statusNodraft
meta_dataNo
attributesNo
categoriesNo
sale_priceNo
descriptionNo
manage_stockNo
stock_statusNoinstock
regular_priceNo
stock_quantityNo
short_descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already say this is a non-read-only, non-idempotent, non-destructive create, so they carry the safety profile; the description adds nothing beyond that. It omits that the product is created as a draft by default, what happens if a variation product is created without variations, and whether any data validation or error behavior applies.

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?

Two tight sentences with the verb and scope front-loaded and no filler. The '[UNIFIED]' tag is the only unnecessary element.

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?

For a 15-parameter mutation tool with no output schema and zero schema descriptions, the definition is too thin. An agent cannot determine required-parameter meaning, string encoding for complex fields, or draft-by-default behavior from what is written.

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 0% across 15 parameters, so the description must carry the load, and it only lists field areas rather than semantics. It never explains the required 'site' parameter, what format categories/tags/meta_data/attributes strings take, or how regular_price vs sale_price interact with product type.

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 gives a specific verb and resource ('Create a new WooCommerce product') and enumerates the supported capability areas: pricing, inventory, categories, tags, descriptions, meta_data, and simple vs variable types. That is enough to distinguish it from update_product or create_product_variation, though the '[UNIFIED]' prefix is unexplained noise.

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 when-to-use guidance at all: nothing says to prefer this over woocommerce_create_product_variation for variable products, or over update_product for existing items. No prerequisites (store/site context, permissions, whether categories or tags must already exist) are stated.

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