Skip to main content
Glama
Sign In
stripe-mcp-server

stripe-mcp-server

by udaykapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Checkout Sessions

list_checkout_sessions
Read-only

Retrieve a list of Stripe Checkout sessions with filters by customer, payment intent, subscription, or status to manage payment flows.

Instructions

List Checkout sessions with optional filtering.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_checkout_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerNoFilter by customer ID
payment_intentNoFilter by PaymentIntent ID
subscriptionNoFilter by Subscription ID
statusNoFilter by session status
limitNoResults per page
starting_afterNoPagination cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already indicates safe reading. The description adds no additional behavioral context (e.g., pagination defaults, rate limits), but does not contradict the annotation.

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 wasted words. Every element ('List', 'Checkout sessions', 'optional filtering') adds value.

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?

The combination of schema (parameter descriptions) and annotations (readOnly) covers the tool's behavior well. Lacks explicit mention of return format or pagination nuances, but these are implied by the schema's pagination parameters.

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?

With 100% schema coverage, the input schema fully describes each parameter. The description's mention of 'optional filtering' is redundant but not harmful. Baseline 3 is appropriate.

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?

The description clearly states the verb 'List' and the resource 'Checkout sessions', with a hint of optional filtering. This directly distinguishes it from other list_* sibling tools that target different resources.

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 guidance is provided on when to use this tool versus alternatives like list_payment_intents or list_invoices. The description does not mention any context-specific conditions or exclusions.

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