Frontman for WordPress

wc_get_product_variation

Read-onlyIdempotent

Gets one WooCommerce product variation. Mirrors woocommerce-mcp-server method get_product_variation using local WordPress authentication; no WooCommerce REST API keys are required.

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_id": "<site_id>",
      "productId": "<productId>",
      "variationId": "<variationId>"
    },
    "name": "wc_get_product_variation"
  }
}

Input Schema

Name	Required	Description
`site_id`	Yes	The connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
`productId`	Yes	The parent product ID.
`variationId`	Yes	The product variation ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds genuine value by explaining it uses local WordPress authentication and needs no WooCommerce REST API keys, which is context an agent could not get from annotations — but it says nothing about behavior on an invalid or missing variation ID.

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 what before the implementation note. The second sentence's reference to the upstream server method name is of limited value to an agent, but the same sentence earns its place by establishing the auth model.

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?

For a three-parameter read tool with full schema coverage and complete annotations, the description is adequate to call it correctly. However, with no output schema present, it gives no indication of the shape of the returned variation object, leaving the agent to discover the response structure at call time.

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%, with site_id, productId and variationId each documented, so the schema carries the semantic load. The description adds no parameter meaning beyond the schema, which is the expected baseline here.

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 opens with a specific verb and resource ('Gets one WooCommerce product variation'), and the word 'one' signals it is a single-record fetch rather than the list operation in wc_get_product_variations. It stops short of explicitly contrasting with that sibling, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus wc_get_product_variations or wc_get_product, and no preconditions beyond an authentication note. The only actionable hint ('call list_sites first') lives in the parameter schema, not the description.

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

All Frontman for WordPress tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.