Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_get_order_refunds

Read-onlyIdempotent

Retrieves refunds for a WooCommerce order. Mirrors woocommerce-mcp-server method get_order_refunds 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>",
      "orderId": "<orderId>"
    },
    "name": "wc_get_order_refunds"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number.
filtersNoWooCommerce REST API filters.
orderIdYesThe order ID.
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.

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 readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds a genuinely useful fact beyond the annotations: this uses local WordPress auth and requires no WooCommerce REST API keys. It does not describe pagination behavior, default page size, or ordering, which matter for a paged list endpoint.

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, with no wasted wording. The second sentence on the mirrored upstream method is slightly internal-facing but still conveys parity and auth behavior.

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?

With no output schema, the description should say something about the shape of the returned refund list, and the free-form filters object is undocumented anywhere. For a paginated list tool with an open-ended nested filter parameter and no output schema, these are meaningful gaps.

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 including site_id and orderId are documented in the schema, which sets the baseline at 3. The description adds no meaning about the filters object, which has an empty properties schema allowing arbitrary keys, nor about how page/perPage interact.

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 refunds for a WooCommerce order") and clarifies the authentication mechanism. It does not, however, distinguish itself from the singular sibling wc_get_order_refund, leaving the plural-vs-single distinction to be inferred from the 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?

No when-to-use guidance and no alternatives named. An agent cannot tell from the description whether to use this list-style tool or wc_get_order_refund for a specific refund, nor when pagination is appropriate; the only contextual guidance is the authentication note.

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