Skip to main content
Glama

stripe_recreate_webhook

Recreates a site's Stripe webhook by creating a new endpoint, deleting older endpoints for the site URL, and storing the new signing secret on the site; requires confirm:true.

Instructions

Recreate this site's Stripe webhook with the gateway's own routine: a new endpoint is created first, then older endpoints for this site's URL are deleted, and the new signing secret is stored on the site (never returned). Use when stripe_list_webhooks shows no enabled configured endpoint. Needs confirm:true; audit-logged.

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>",
      "confirm": "<confirm>"
    },
    "name": "stripe_recreate_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
confirmYesMust be true: this changes the live Stripe account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the create-before-delete ordering, that older endpoints get destroyed, that the signing secret is stored but never returned, that confirm:true is mandatory because the live Stripe account changes, and that the action is audit-logged. Not covered: required permissions, rollback/failure behavior if the delete step fails, or rate limits.

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?

Roughly fifty words, front-loaded with the operation and its sequence, then the precondition, then the safety gate. No sentence is filler — each one adds a distinct operational fact.

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 destructive mutation with no annotations and no output schema, this covers the sequence, side effects, secret handling, the confirm gate, and the precondition. The remaining gap is failure semantics — what state the site is left in if the new endpoint is created but deletion or secret storage fails.

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% and both parameters are already documented, including the const:true constraint on confirm, so the baseline is 3. The description adds only the reason confirm matters (it changes the live Stripe account) and that 'site' maps to the endpoint URL being managed, which is marginal beyond the schema.

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?

Names a specific verb and resource (recreate the site's Stripe webhook) and then spells out the operation's shape: create a new endpoint, delete older endpoints for the site's URL, store the new signing secret. That is distinguishable at a glance from stripe_list_webhooks and the other Stripe siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives an explicit trigger condition tied to a named sibling: 'Use when stripe_list_webhooks shows no enabled configured endpoint.' The inverse (do not run while a working endpoint exists) is implied by that precondition rather than stated, so there is a small gap but the routing guidance is clear.

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