Skip to main content
Glama

stripe_list_webhooks

Lists Stripe webhook endpoints for a site, showing IDs, URLs, status, API version, event counts, and which endpoint delivers to the site's gateway.

Instructions

Webhook endpoints of the Stripe account: id, url, status, api_version, number of events; configured:true marks the endpoint that delivers to this site's gateway URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "stripe_list_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden alone. It usefully discloses the returned field set and explains the otherwise opaque 'configured:true' marker (the endpoint delivering to this site's gateway URL), but says nothing about account scope vs per-site filtering, pagination, or read-only/auth expectations.

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

Conciseness4/5

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

A single dense sentence that front-loads the resource and the field inventory, with the 'configured' flag explained immediately after. Slightly terse colon-list phrasing makes it read a bit like a spec dump, but no sentence is wasted.

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 one-parameter read listing with no output schema and no annotations, the description covers what comes back and what the key derived field means. Remaining gaps (pagination, whether all account endpoints or only this site's are returned) are minor but real.

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 coverage is 100% and the single 'site' parameter is documented in the schema itself. The description only indirectly ties the result to the current site through the 'this site's gateway URL' phrasing and adds no format or lookup detail beyond the schema. Baseline 3 applies.

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?

Names a specific resource (Stripe webhook endpoints) and enumerates the returned fields: id, url, status, api_version, event count, plus the synthetic 'configured' flag. The verb 'list' is only implicit via the tool name, and it does not explicitly contrast with the sibling stripe_recreate_webhook, so it stops short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of the write-oriented sibling stripe_recreate_webhook as the alternative for creating or repairing endpoints. The agent must infer that this is the read path for webhook configuration.

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