Skip to main content
Glama

wc_update_product

Update a WooCommerce product's regular price, sale price, stock quantity, or description. Use it for product data changes; publish status is not changed and write mode is required.

Instructions

Update a WooCommerce product's price, sale price, stock or description. Cannot change publish status. Requires write mode.

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": {
      "id": "<id>"
    },
    "name": "wc_update_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
sale_priceNoEmpty string clears the sale price
descriptionNo
regular_priceNo
stock_quantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose two real constraints: publish status cannot be changed, and write mode is required. It still omits whether omitted fields are preserved on partial updates, whether the operation is idempotent, and what failures look like for a mutation tool.

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 short sentences, front-loaded with the mutation scope and followed by the key constraint; almost no wasted wording. The phrasing 'Cannot change publish status' is slightly terse but readable.

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 write operation with no annotations, no output schema, and five parameters at 20% description coverage, the definition is thin. It does not explain partial-update behavior, validation of price formats, or what the call returns, leaving the agent to guess at important mutation semantics.

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 coverage is only 20%, so the description needs to compensate and largely does not: it names the updatable concepts but gives no format guidance for regular_price or sale_price strings, no indication of currency or decimal conventions, and never mentions the required id. The only useful clearing rule for sale_price lives in the schema, not the description.

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 states a specific verb and resource ('Update a WooCommerce product') and enumerates the mutable fields (price, sale price, stock, description), which an agent can distinguish from wc_create_product or wc_get_product without opening a schema. Differentiation from siblings is implicit rather than stated.

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

Usage Guidelines3/5

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

'Requires write mode' tells the agent about a precondition for use, which is genuine guidance. However, there is no explicit statement of when to choose this over wp_update_post or wc_create_product, nor any exclusion beyond the publish-status restriction.

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