Skip to main content
Glama
r28ai

stripe-billing-ops-mcp

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

stripe_payouts_list

Read-onlyIdempotent

List payouts sent to your bank account or card, sorted by most recent, to track and reconcile incoming funds.

Instructions

List payouts to your own bank account or card, most recently created first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoA limit on the number of objects to be returned, between 1 and 100. Defaults to 10.
statusNoOnly return payouts with this status. A payout Stripe has sent to the bank but not settled reports 'in_transit' on the object, which this filter does not document.
createdNoOnly return records created in this window.
arrivalDateNoOnly return payouts expected to arrive in this window.
destinationNoOnly return payouts sent to this external account: a bank account or card, not a connected account.
endingBeforeNoA cursor for use in pagination: an object ID that defines your place in the list. Returns the page before the named object. Mutually exclusive with starting_after.
startingAfterNoA cursor for use in pagination: an object ID that defines your place in the list. To get the next page, pass the id of the last object in the current page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds only the default sort order ('most recently created first'); it says nothing about pagination mechanics or result size beyond what the schema provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no filler. The resource is named immediately and the scoping/ordering detail follows compactly.

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 list tool with full schema coverage and annotations covering safety, the definition is nearly sufficient. The main gap is the absence of guidance on pagination workflow and how this list differs from related payout/balance/transaction lists, but nothing critical is missing.

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 seven parameters (limit, status, created, arrivalDate, destination, cursors) are already documented in the schema with good detail. The description adds no parameter-level meaning beyond the schema, so the baseline 3 is appropriate.

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 (list) and resource (payouts), plus a distinguishing scope: 'to your own bank account or card' (as opposed to connected accounts). It also communicates default ordering, but does not name a sibling tool to contrast against, leaving differentiation to be inferred.

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?

The description gives no explicit when-to-use guidance and never mentions alternatives such as stripe_balance_transactions_list or stripe_disputes_list. 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