Skip to main content
Glama

stripe_list_charges

Retrieve recent Stripe charges with amounts, statuses, and WooCommerce order IDs to review payments, refunds, and failures without exposing customer or card data.

Instructions

Recent Stripe charges: id, amount, currency, status, created, paid/refunded, payment method type, outcome, failure code/message, WooCommerce order_id. No customer personal data or card details.

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

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

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose two useful traits: results are recent/newest-first records and the payload deliberately excludes customer personal data and card details, which matters for privacy-sensitive agents. It does not cover read-only semantics explicitly, what happens if the site has no Stripe connection, or how deep 'recent' reaches beyond the limit parameter.

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 resource, followed by a compact field manifest and the privacy caveat. The field enumeration is dense but each item tells the agent what data is available, so nothing is wasted.

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?

With no output schema, the description correctly compensates by listing the returned fields, so an agent knows what it will get back. For a two-parameter read tool this is nearly sufficient; only the meaning of 'Recent' relative to the limit parameter is left implicit.

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% – both 'site' (with a pointer to list_sites) and 'limit' (1-100, default 20, newest first) are fully documented in the schema. The description adds no parameter-level detail beyond what is already structured, so the baseline of 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?

The description names the resource (Stripe charges) and enumerates the returned fields (id, amount, currency, status, created, refund state, payment method type, outcome, failure info, WooCommerce order_id), which makes it clearly distinct from siblings like stripe_list_refunds. It never uses an explicit verb like 'list' and 'Recent' is not defined, but the resource and scope are still legible.

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 on when to use this versus alternatives such as stripe_list_refunds or woo_helper_get_stripe, and no statement of prerequisites. The only scoping hint is the word 'Recent', which is not defined anywhere in the description.

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