Skip to main content
Glama

wc_get_product

Retrieve a single WooCommerce product and its full description by ID. Use it to fetch product details for AI assistants managing store data through the WordPress REST API.

Instructions

Get one WooCommerce product with its description.

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_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and delivers little: no statement about read-only safety, authentication requirements, or what happens when the ID doesn't exist. The only behavioral hint is 'with its description', which touches part of the payload but not error or permission behavior.

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?

One short sentence with the verb and resource front-loaded and no filler; there is nothing to trim. Its brevity comes at the cost of substance, but the sentence itself is well-formed.

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 simple single-resource getter with one parameter and no output schema, the description is minimally viable. It still omits what the returned product object contains beyond a description and what identifies the product, which matters because there are no annotations to fill the gap.

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 description coverage is 0% for the single required 'id' parameter, and the description never explains that it is a product ID integer (nor rules out SKU or slug). With one undocumented parameter the schema alone leaves the agent guessing, so the description should have compensated and does not.

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 (get) and resource (one WooCommerce product) and adds scope information (single item, includes the description field), which distinguishes it implicitly from the list-style siblings. It stops short of naming a sibling such as wc_list_products or wc_get_order, so an agent must infer the boundary.

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 explicit when-to-use guidance: nothing says to call this when you have a known product ID versus using wc_list_products to search. The word 'one' hints at single-item retrieval, but alternatives and preconditions are left entirely to inference.

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