Skip to main content
Glama

stripe_list_refunds

Retrieve recent Stripe refunds with amount, currency, status, reason, charge, and WooCommerce order ID to review refund activity; read-only and does not create refunds.

Instructions

Recent Stripe refunds: id, amount, currency, status, created, charge, reason, WooCommerce order_id. Read-only; refunds are not created here.

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": "<site>"
    },
    "name": "stripe_list_refunds"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
limitNoHow many, newest first (1-100, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the safe read-only nature and explicitly excludes refund creation, which is genuinely useful. It omits auth/permission requirements, whether results are scoped to the required site parameter only, and any pagination or rate-limit behavior beyond what the schema states.

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 clauses with no filler; the resource and returned fields are front-loaded and the read-only caveat follows. The field enumeration is dense but serves a real purpose given there is no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, listing the returned fields is a substantive contribution, and the read-only disclaimer covers the main behavioral risk. Remaining gaps (auth needs, whether ordering is strictly newest-first, whether non-refunded charges appear) are minor for a simple two-parameter list tool.

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 both the required 'site' and the 'limit' bounds/ordering are already fully documented in the schema. The description adds no additional meaning about parameters, which is acceptable at this coverage level.

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 names the resource (Stripe refunds) and enumerates the fields returned (id, amount, currency, status, created, charge, reason, WooCommerce order_id), so an agent knows exactly what it is retrieving. It is clearly distinguishable from stripe_list_charges by resource, though it never uses an explicit verb like 'list' and leans on the name to convey the operation.

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

Usage Guidelines3/5

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

The clause 'Read-only; refunds are not created here' rules out a plausible confusion (creating refunds) but gives no positive when-to-use guidance, no prerequisites, and no comparison to any alternative tool. Usage is only implied by the resource name.

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

Deploy Server

Other Tools