Skip to main content
Glama

WooCommerce: Create product category

woocommerce_create_product_category

Create a new WooCommerce product category and assign a parent to build hierarchical category structures. Use it to organize products under the right category or subcategory.

Instructions

[UNIFIED] Create a new WooCommerce product category. Supports hierarchical categories with parent-child relationships.

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_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
siteYes
parentNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write-safety profile is covered. The description adds that parent-child hierarchy is supported, which is real context, but it omits the practical consequence of non-idempotency (duplicate categories on repeat calls) and any error or permission behavior.

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 with the action front-loaded and the hierarchy capability immediately after; there is no filler or redundancy. The '[UNIFIED]' tag is the only questionable token.

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 4-parameter creation tool with zero schema description coverage and no output schema, the definition is too thin: an agent gets no explanation of the store-scoping parameter and no notion of what the call returns (e.g., the new category ID) or how failures surface.

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 4 parameters, so the description must carry the meaning. It only gestures at 'parent' via the hierarchy sentence and says nothing about what 'site' identifies, what 'description' populates, or any format constraints for 'name'.

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 new WooCommerce product category'), which clearly separates it from the delete/list/update category siblings without needing to name them. It adds a scope note about hierarchy, though it does not explicitly contrast with wordpress_create_category or woocommerce_create_product_attribute.

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 choose this over wordpress_create_category or the attribute/variation creation siblings, and no prerequisites such as which store 'site' must reference or what happens if the category already exists. The agent must infer usage entirely from the name.

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