Checkout Page

delete_webhook

Destructive

Delete a webhook endpoint by id. Deliveries stop immediately and the endpoint disappears from list_webhooks; its delivery history is kept. Destructive and irreversible. Confirm with the user and use list_webhooks to find the id first.

Input Schema

Name	Required	Description	Default
`webhookId`	Yes	The webhook ID, as returned by create or list.

Output Schema

Name	Required	Description	Default
`data`	Yes	A webhook endpoint subscribed to one or more events.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026

changedOutput schema / properties / data / properties / events / items / description

Previous value: -"An event a webhook can subscribe to. Valid values: webhook.test, customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, payment.canceled, booking.abandoned, booking.created, booking.paid, booking.canceled, ticket.created, submission.created, submission.updated, submission.canceled, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired. `webhook.test` is the payload sent by the dashboard's test-delivery action."New value: +"An event a webhook can subscribe to. Valid values: webhook.test, customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, payment.canceled, booking.abandoned, booking.created, booking.paid, booking.canceled, ticket.created, ticket.canceled, submission.created, submission.updated, submission.canceled, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired. `webhook.test` is the payload sent by the dashboard's test-delivery action."

changedOutput schema / properties / data / properties / events / items / enum

Previous value: -[
-  "webhook.test",
-  "customer.created",
-  "customer.updated",
-  "payment.abandoned",
-  "payment.created",
-  "payment.paid",
-  "payment.canceled",
-  "booking.abandoned",
-  "booking.created",
-  "booking.paid",
-  "booking.canceled",
-  "ticket.created",
-  "submission.created",
-  "submission.updated",
-  "submission.canceled",
-  "checkout_page.created",
-  "checkout_page.updated",
-  "product.created",
-  "product.updated",
-  "subscription.abandoned",
-  "subscription.created",
-  "subscription.trialing",
-  "subscription.scheduled",
-  "subscription.active",
-  "subscription.completed",
-  "subscription.canceled",
-  "subscription.expired"
-]New value: +[
+  "webhook.test",
+  "customer.created",
+  "customer.updated",
+  "payment.abandoned",
+  "payment.created",
+  "payment.paid",
+  "payment.canceled",
+  "booking.abandoned",
+  "booking.created",
+  "booking.paid",
+  "booking.canceled",
+  "ticket.created",
+  "ticket.canceled",
+  "submission.created",
+  "submission.updated",
+  "submission.canceled",
+  "checkout_page.created",
+  "checkout_page.updated",
+  "product.created",
+  "product.updated",
+  "subscription.abandoned",
+  "subscription.created",
+  "subscription.trialing",
+  "subscription.scheduled",
+  "subscription.active",
+  "subscription.completed",
+  "subscription.canceled",
+  "subscription.expired"
+]

Changed2 schema fields changedOct 30, 2026

changedOutput schema / properties / data / properties / events / items / description

Previous value: -"An event a webhook can subscribe to. Valid values: webhook.test, customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, booking.abandoned, booking.created, booking.paid, ticket.created, submission.created, submission.updated, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired. `webhook.test` is the payload sent by the dashboard's test-delivery action."New value: +"An event a webhook can subscribe to. Valid values: webhook.test, customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, payment.canceled, booking.abandoned, booking.created, booking.paid, booking.canceled, ticket.created, submission.created, submission.updated, submission.canceled, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired. `webhook.test` is the payload sent by the dashboard's test-delivery action."

changedOutput schema / properties / data / properties / events / items / enum

Previous value: -[
-  "webhook.test",
-  "customer.created",
-  "customer.updated",
-  "payment.abandoned",
-  "payment.created",
-  "payment.paid",
-  "booking.abandoned",
-  "booking.created",
-  "booking.paid",
-  "ticket.created",
-  "submission.created",
-  "submission.updated",
-  "checkout_page.created",
-  "checkout_page.updated",
-  "product.created",
-  "product.updated",
-  "subscription.abandoned",
-  "subscription.created",
-  "subscription.trialing",
-  "subscription.scheduled",
-  "subscription.active",
-  "subscription.completed",
-  "subscription.canceled",
-  "subscription.expired"
-]New value: +[
+  "webhook.test",
+  "customer.created",
+  "customer.updated",
+  "payment.abandoned",
+  "payment.created",
+  "payment.paid",
+  "payment.canceled",
+  "booking.abandoned",
+  "booking.created",
+  "booking.paid",
+  "booking.canceled",
+  "ticket.created",
+  "submission.created",
+  "submission.updated",
+  "submission.canceled",
+  "checkout_page.created",
+  "checkout_page.updated",
+  "product.created",
+  "product.updated",
+  "subscription.abandoned",
+  "subscription.created",
+  "subscription.trialing",
+  "subscription.scheduled",
+  "subscription.active",
+  "subscription.completed",
+  "subscription.canceled",
+  "subscription.expired"
+]

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description still adds real behavioral detail beyond that: deliveries cease immediately, the endpoint vanishes from list_webhooks, and delivery history is retained — the last being a non-obvious side effect an agent would otherwise have to guess. "Irreversible" mildly restates the destructive hint, keeping this just short of 5.

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?

Four short sentences, front-loaded with purpose and followed by effects, then the safety instruction. Nothing is padding, though "Destructive and irreversible" overlaps partly with the destructiveHint annotation rather than adding fully new information.

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

Completeness5/5

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

For a destructive one-parameter mutation, the description covers side effects, retained data, irreversibility, and the lookup/confirmation workflow. An output schema exists, so return values need not be explained, and nothing an agent needs before calling is missing.

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 pattern plus "as returned by create or list" already documents the single webhookId parameter. The description only reinforces where to obtain the id, so the baseline of 3 is appropriate — the schema carries the load.

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?

States a specific verb and resource ("Delete a webhook endpoint by id"), which immediately separates it from siblings like delete_product or update_webhook. The scope (single endpoint identified by id) is unambiguous.

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

Usage Guidelines5/5

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

Explicitly routes the agent to list_webhooks to obtain the id, and adds a procedural prerequisite to confirm with the user before invoking. This is both when-to-use guidance and an invocation precondition rather than vague context.

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

All Checkout Page tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?