Skip to main content
Glama
Jacques-Murray

WooCommerce MCP Server

Create WooCommerce Product

woocommerce_create_product

Add a product to your WooCommerce store with name, price, SKU, description, images, and inventory settings.

Instructions

Create a new product in the WooCommerce catalog.

Args:

  • name (string, required): Product name

  • type ('simple'|'grouped'|'external'|'variable'): default 'simple'

  • status ('draft'|'pending'|'private'|'publish'): default 'publish'

  • description / short_description (string, optional): HTML allowed

  • sku (string, optional): must be unique store-wide

  • regular_price / sale_price (string, optional): numeric strings

  • manage_stock (boolean), stock_quantity (number), stock_status (string)

  • category_ids / tag_ids (number[]): assign existing taxonomy terms

  • image_urls (string[]): externally hosted image URLs, WooCommerce will import them

  • weight (string, optional)

  • response_format ('markdown'|'json'): default 'markdown'

Returns: The newly created product object with its assigned ID.

Examples:

  • Use when: "add a new t-shirt product priced at $25" -> name="T-Shirt", regular_price="25.00"

  • Don't use when: creating a variation of an existing variable product (use woocommerce_create_product_variation)

Error Handling:

  • Returns "Error: Bad request (400)" if sku is already in use by another product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuNoStock keeping unit, must be unique in the store
nameYesProduct name
typeNoProduct type (default: simple)simple
statusNoProduct status (default: publish)publish
weightNoWeight as numeric string, in the store's configured weight unit
tag_idsNoTag IDs to assign to the product
image_urlsNoImage URLs to attach to the product, in display order
sale_priceNoSale price as numeric string, e.g. '19.99'
descriptionNoFull product description (HTML allowed)
category_idsNoCategory IDs to assign to the product
manage_stockNoWhether to track stock quantity for this product
stock_statusNoStock status
regular_priceNoRegular price as numeric string, e.g. '29.99'
stock_quantityNoStock quantity (only used if manage_stock is true)
response_formatNoOutput format: 'markdown' for human-readable text or 'json' for machine-readable structured datamarkdown
short_descriptionNoShort product description (HTML allowed)
Behavior5/5

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

Annotations provide minimal info (readOnlyHint=false, etc.), but the description adds significant behavioral details: image URLs are imported, response can be markdown or JSON, SKU uniqueness enforcement, and error handling. No contradictions.

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?

Well-structured with clear sections (Args, Returns, Examples, Error Handling). However, the Args list is lengthy and largely repeats schema information, which could be more concise. Still, it is front-loaded and easy to parse.

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

Completeness5/5

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

Given no output schema and 16 parameters, the description covers return value, error scenarios, and usage examples. It provides sufficient context for an AI agent to correctly select and invoke the tool, including differentiation from sibling tools.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds value beyond schema by providing examples, default values, constraints (e.g., 'must be unique store-wide' for SKU, 'numeric strings' for prices), and error handling context. The Args section summarizes parameters effectively.

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?

The description clearly states 'Create a new product in the WooCommerce catalog' with a list of parameters and examples. It distinguishes from sibling tools like woocommerce_create_product_variation by explicitly stating not to use for creating variations.

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

Usage Guidelines5/5

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

Includes explicit examples of when to use ('add a new t-shirt product') and when not to use ('creating a variation... use woocommerce_create_product_variation'). Also covers error handling for duplicate SKU, guiding proper invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jacques-Murray/woocommerce-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server