Frontman for WordPress

wc_get_attribute_terms

Read-onlyIdempotent

Retrieves terms for a WooCommerce product attribute. Mirrors woocommerce-mcp-server method get_attribute_terms 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>",
      "attributeId": "<attributeId>"
    },
    "name": "wc_get_attribute_terms"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number.
`filters`	No	WooCommerce REST API filters.
`perPage`	No	Number of results per page.
`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.
`attributeId`	Yes	The product attribute ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

C2.9/5.0

Behavior2/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 safety is covered. The description adds the useful auth detail that local WordPress authentication is used and no WooCommerce REST API keys are needed. It says nothing about pagination behavior, default page size, or what happens when attributeId does not exist — relevant for a paginated list 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 purpose. The second sentence is somewhat implementation-referential ('Mirrors woocommerce-mcp-server method') but does convey the auth model, so it earns most of its place.

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?

A read-only list tool with full schema coverage and a complete annotation set needs little more, and the auth note is a genuine addition. Still missing is disambiguation from the singular `wc_get_attribute_term` and any note on pagination semantics for the page/perPage pair.

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% across all five parameters, including the nested free-form `filters` object and the site_id prerequisite, so the schema carries the semantic load. The description adds no parameter-level meaning beyond it; baseline 3 applies.

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 terms for a WooCommerce product attribute.' An agent knows exactly what kind of object is returned. However, the description does not distinguish this list operation from the sibling `wc_get_attribute_term` (singular), so the agent must infer the plurality distinction from the tool name alone.

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 guidance about when to use this versus `wc_get_attribute_term` or `wc_get_product_attribute`. The only operational hint ('Call list_sites first') lives in the site_id parameter description, not in the tool description itself.

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.