Checkout Page

get_webhook

Read-only

Fetch one webhook by id - its URL, subscribed events, status and delivery counters. The signing secret is never returned and custom header values are shown as [hidden]; headers are viewed and edited at the returned dashboardUrl. Use list_webhooks to find the id. Read-only.

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

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so the closing "Read-only." is redundant. However, the description adds genuinely new behavior with annotations absent: the signing secret is never returned, custom header values are redacted as `[hidden]`, and headers must be managed via the returned `dashboardUrl`. That redaction disclosure is the kind of thing an agent cannot infer from structured fields.

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?

Three short sentences, front-loaded with purpose, then the redaction caveat, then the sibling pointer. Nothing padding; even the somewhat redundant "Read-only" is a single clause.

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?

With an output schema present, the description needn't enumerate return values, and it correctly focuses on the surprises an agent would hit (hidden secret, masked headers). What's missing is minor: error behavior for a not-found or malformed id, and confirmation of what `status` values mean.

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 parameter already documents the 24-hex format and its origin. The description only restates the id concept and cross-references list_webhooks, so it adds little parameter-level meaning beyond the schema. Baseline 3 is appropriate.

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?

Specific verb and resource ("Fetch one webhook by id") immediately followed by the fields returned (URL, subscribed events, status, delivery counters). It is clearly distinguished from the sibling list_webhooks, and even from update_webhook by noting that editing happens elsewhere.

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 a concrete prerequisite path: "Use list_webhooks to find the id." That is enough for an agent to route correctly between single-fetch and list. It stops short of stating when *not* to call it (e.g., bulk inspection, or which sibling to use for secret rotation), so it is not a full 5.

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?