Create a WooCommerce product with customizable attributes including name, price, stock, categories, images, and metadata.
Create a WooCommerce product
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Product name | |
| type | No | simple | |
| status | No | publish | |
| regular_price | No | ||
| sale_price | No | ||
| description | No | ||
| short_description | No | ||
| sku | No | ||
| manage_stock | No | ||
| stock_quantity | No | ||
| stock_status | No | instock | |
| categories | No | ||
| tags | No | ||
| images | No | ||
| attributes | No | ||
| meta_data | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations given, and the description does not disclose side effects, permissions required, or any behavioral traits. It is a single line with no additional context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short, which is efficient but arguably too under-specified for a tool with 16 parameters. It is front-loaded with the purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 16 parameters, no output schema, and no annotations. The description is a single sentence that does not cover return values, relationships with other tools, or any contextual details. Highly incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 6% (only 'name' has a description). The description adds no information about parameters, leaving 15 parameters undocumented in both schema and description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool creates a WooCommerce product, distinguishing it from update/delete and other product-related tools. The verb 'create' is specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like updating or deleting products. No prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cvrt-jh/wordpress-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server