Skip to main content
Glama

payments_transactions

Read-onlyIdempotent

List recent charges on the project owner's connected account. Returns Stripe's native cursor pagination — starting_after set to the previous response's next_cursor fetches the next page. Default page size 20, max 100. env=prod lists live-mode charges; default env=dev lists test-mode.

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": {
      "project_id": "<project_id>"
    },
    "name": "payments_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo'dev' (default — test-mode) or 'prod' (live mode).
limitNoPage size (1-100). Default 20.
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).
starting_afterNoStripe cursor — the previous page's `next_cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), and the description adds genuinely new behavior: Stripe-native cursor pagination, the next_cursor chaining rule, and the dev/test vs live-mode data separation via env. It stops short of mentioning rate limits or that the connected account must already be provisioned.

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?

Four short sentences, front-loaded with purpose and then pagination mechanics; nothing is bloated. Minor redundancy in restating the default and max page size that the schema already documents.

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?

For a read-only Stripe passthrough with no output schema, the description gives enough to call it correctly: cursor chaining, page size bounds, and environment selection. It does not describe the shape of a returned charge object, but that omission is reasonable given the native Stripe format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it explains that starting_after must be the previous response's next_cursor, a relationship that only exists at runtime since there is no output schema. The limit and env semantics are mostly restated from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List recent charges') plus the scope ('project owner's connected account'), which is enough to separate it from siblings like payments_checkout, payments_events, and payments_status without opening any schema.

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 phrase 'list recent charges' implies when to reach for it, and the env note clarifies which data set you get, but there is no explicit guidance on when to prefer this over payments_events or payments_checkout, and no prerequisites or exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources