Skip to main content
Glama

woo_list_variations

Retrieve the purchasable, visible variations of a WooCommerce variable product by parent product ID and site so you can inspect available options.

Instructions

List the available (purchasable, visible) variations of a variable product

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>",
      "product_id": "<product_id>"
    },
    "name": "woo_list_variations"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
product_idYesParent product ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.14.0
    • changedInput schema / properties / product_id / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "product_id"
      -]New value: +[
      +  "site",
      +  "product_id"
      +]
  3. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose one genuinely useful trait — only available, purchasable, visible variations are returned, so hidden or out-of-stock ones are filtered out — but says nothing about pagination, result limits, permissions, or ordering. Read-only behavior is only implied by the verb 'List'.

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?

A single front-loaded sentence with no redundant wording, and the filtering qualifier sits immediately next to the resource it modifies. It is efficient but slightly under-specified for the amount of behavior an agent needs.

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

Completeness3/5

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

This is a simple two-parameter read tool, so a short description is defensible, but with no annotations and no output schema the description never indicates what a variation record contains (attributes, price, stock) or whether results are paginated or truncated.

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

Parameters3/5

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

Schema description coverage is 100% (site is documented as 'Site id (see list_sites)', product_id as 'Parent product ID'), so the schema already does the heavy lifting. The description adds the meaning that product_id must reference a variable product, but gives no further syntax or format detail beyond that.

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 (List) and a specific resource (variations of a variable product), and the parenthetical narrows it to purchasable/visible variations. That is enough to separate it from woo_list_products, though it never names a sibling or an alternative entry point.

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?

Usage is only implied: the agent must infer that this applies when it already has a variable product ID and needs its child variations. There is no explicit when-to-use, no exclusion (e.g. 'do not use for simple products'), and no stated prerequisite such as the product needing to be of type variable.

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