get_webhook
Retrieve configured webhook URLs for a channel and their delivery status to see which endpoints receive events and which are skipped.
Instructions
Return the webhook URL(s) currently configured for this channel, plus delivery status for each URL.
webhookUrl is a string when a single URL is set, an array of strings when
multiple URLs are configured, or null if none is set.
Prefer webhookStatuses. The circuit breaker is per URL, not per channel.
If 1 of 4 URLs is sticky-disabled, that URL is skipped; the other three still
receive events. Send/receive are not affected.
Channel-level haveDisabledWebhooks, circuitState, reason, fails,
trips, and timestamps are a compatibility summary of one URL (the first
sticky-disabled URL, else the first configured URL). They are not "the channel
is dead".
haveDisabledWebhooks—truewhen at least one URL inwebhookUrlis sticky auto-disabled. Live URLs still get events.circuitState— compressed scalar for that same primary URL:ok|degraded|open|half_open|disabled.disabledWebhooks— currently configured URLs that are sticky-disabled (subset ofwebhookUrl).webhookStatuses— one row per currently configured URL. Use this array to see which endpoints are live vs skipped.fails/trips/firstFailAt— diagnostics for support, not product UI.fails= failures in a rolling ~10 minute window (not lifetime).trips= failed recovery probes on the 15 min → 1 h → 6 h schedule (sticky disable after 3). Clients can ignore these and usewebhookStatuses+disabledWebhooksonly.
Sticky disable skips delivery; it does not unconfigure the URL (it stays in
webhookUrl). Re-enable with POST /webhook or POST /settings. Those
endpoints replace the whole list — with multiple URLs, send the full array.
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": "get_webhook"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||