wordpress_wc_update_productUpdate WooCommerce product details, including price, stock, or custom fields, by providing the product ID and desired changes.
Update WooCommerce product
| Name | Required | Description | Default |
|---|---|---|---|
| productId | Yes | ||
| updates | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full transparency burden. It only restates the operation without disclosing whether updates are partial or full, what happens on missing products, side effects, or return values. This is essentially no behavioral disclosure.
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 extremely short, but this is under-specification rather than effective conciseness. It provides no structural breakdown of concepts, use cases, or parameter relationships, offering no searchable substance beyond the title.
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?
For a tool with a nested object parameter and no output schema, the description is wholly inadequate. It fails to mention the expected response, error behavior, or the semantic content of 'updates', leaving major gaps for an agent to invoke the tool correctly.
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 description coverage is 0%, and the description provides no parameter information. The 'updates' parameter is an unconstrained free-form object, leaving the agent completely in the dark about valid fields. The description does not compensate at all for the schema's lack of guidance.
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 verb 'update' and a specific resource ('WooCommerce product'), which distinguishes it from create/get/delete siblings. However, it adds no detail about what aspects of the product can be updated, so it stops short of a 5.
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?
The description gives no guidance on when to use this tool versus other product-related tools (e.g., create, delete, get). No contextual or exclusionary information is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.