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

stripe-mcp-server

by udaykapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Events

list_events
Read-only

Retrieve recent Stripe webhook events to debug integrations and monitor event activity.

Instructions

List recent Stripe events (webhook deliveries). Useful for debugging integrations.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by event type, e.g. "payment_intent.succeeded", "customer.created"
limitNoResults per page
starting_afterNoPagination cursor
created_gteNoCreated at or after (Unix timestamp)
created_lteNoCreated at or before (Unix timestamp)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

The description adds minimal behavioral context beyond the readOnlyHint annotation, simply restating the basic function. No additional traits like rate limits or access needs are disclosed.

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?

The description is a single, front-loaded sentence that efficiently conveys the tool's purpose without any fluff or redundant information.

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

Completeness3/5

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

With 5 parameters and no output schema, the description is brief and omits context like pagination, default sorting, or typical response structure, though the schema covers parameter details.

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?

All parameters are fully described in the schema (100% coverage), so the description does not need to add parameter details. It provides no extra semantic value beyond the schema.

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?

The description clearly states it lists events (webhook deliveries) and mentions a use case (debugging), which distinguishes it from other list tools by resource. However, it does not explicitly differentiate from sibling list tools, preventing a 5.

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 description implies usage for debugging integrations but provides no explicit guidance on when to use this tool vs alternatives, nor does it mention exclusion criteria or prerequisites.

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