Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_get_product_variations

Read-onlyIdempotent

Retrieves variations for a WooCommerce product. Mirrors woocommerce-mcp-server method get_product_variations 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>"
    },
    "name": "wc_get_product_variations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number.
filtersNoWooCommerce REST API filters.
perPageNoNumber of results per page.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
productIdYesThe parent product ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, and destructiveHint=false, so the safety profile is covered. The description does add real context beyond the annotations by explaining the authentication model (local WordPress auth, no REST API keys required), which matters for callers. It stops short of describing pagination behavior, default page size, or return shape.

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 tight sentences, front-loaded with the purpose and followed by the auth note. Every sentence earns its place, though the second sentence leans toward implementation trivia ('Mirrors woocommerce-mcp-server method ...') rather than agent-facing guidance.

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 read-only, five-parameter tool with a nested open-ended `filters` object and no output schema, the definition is minimally sufficient but thin: it never explains what the filter object accepts or what the returned variation records look like, and it offers no pagination guidance for a list endpoint.

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%, so all five parameters already carry descriptions, establishing the baseline of 3. The description adds nothing about the semantics of the nested, effectively unfilled `filters` object or about how page/perPage interact, which is where documentation would have helped most.

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 and resource: retrieves variations belonging to a WooCommerce product. That is clear enough to act on, but it does not differentiate from the closer sibling wc_get_product_variation (singular), leaving the agent to infer the plural-vs-singular split on its own.

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?

No when-to-use guidance at all: nothing says when to prefer this bulk listing over wc_get_product_variation, nothing about expected volume, pagination strategy, or result limits. The only routing hint ('Call list_sites first') appears in the schema rather than 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 toolsInspect
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.

Resources