Skip to main content
Glama

stripe_list_customers

List Stripe customers using optional filters like email or pagination cursor. Returns customer ID, name, email, and metadata.

Instructions

List Stripe customers with optional filters. Returns customer ID, name, email, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoFilter customers by exact email address
limitNoNumber of customers to return (1-100). Default: 10
starting_afterNoCursor for pagination — pass the last customer ID from the previous page
Behavior2/5

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

No annotations provided; description does not disclose behavioral traits such as read-only nature, authentication needs, rate limits, or side effects. Only states it returns specific fields.

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?

Description is a single efficient sentence (11 words) that is front-loaded with the action and resource.

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

Completeness2/5

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

Missing explanation of return format (list vs single), pagination behavior beyond schema, and ordering. With no output schema, the description should provide more detail on return values.

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 baseline is 3. Description adds no additional meaning beyond schema; merely mentions 'optional filters' without detailing parameters.

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?

Description clearly states action (List), resource (Stripe customers), and mentions optional filters, distinguishing it from sibling tools like stripe_create_customer or stripe_check_subscription.

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 on when to use this tool vs alternatives, nor any when-not-to-use or prerequisites. Only implied usage for listing customers.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hackerxj2010/mcp-saas-toolkit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server