stripe_list_eventsList Stripe events by type or prefix, and show only those with failing webhook deliveries to identify and resolve delivery problems.
Recent Stripe events. Filter by type ("payment_intent.succeeded") or by prefix ("payment_intent."). only_undelivered=true lists events whose webhook delivery is still failing.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| limit | No | ||
| only_undelivered | No |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It adds useful semantics for only_undelivered and 'recent' scope, but it does not mention ordering, pagination, or the default limit behavior. It is not misleading, but the behavioral disclosure is incomplete.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: it states the scope first, then gives filter usage with concrete examples. Every sentence contributes useful information without repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is sufficient for basic invocation but lacks pagination/ordering details and does not mention stripe_get_event as the alternative for single-event lookups. Given no output schema or annotations, a bit more context would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds real meaning beyond the schema by explaining that type accepts both exact values and prefixes, and by defining only_undelivered. Limit is not described in prose, but its name and schema constraints make its purpose clear.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies this as a listing operation for recent Stripe events and explains the available filtering by type or prefix. It is readily distinguishable from stripe_get_event, which retrieves a single event.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context for when to use the tool: to list recent events with optional type/prefix filtering or undelivered-webhook filtering. It does not explicitly name alternatives or exclusions, but the context is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.