MCP tools: webhooks
Four tools help when a webhook seems to have stopped: find it, see what was sent and what came back, send a test, then resend what failed.
On this page 2
Webhooks themselves are added in Dashboard → Settings → Webhooks (how webhooks work). These tools never return a signing secret or a payload, and they show a receiver's site (for example zapier.com), not its full URL, because receiver URLs often carry a secret.
The tools
| Tool | What it does | Changes something? |
|---|---|---|
list_webhooks |
Your webhooks: id, receiver site, the events each one gets, and whether it is on | No |
list_webhook_deliveries |
A webhook's deliveries from the last 30 days, newest first: status (pending, delivered, failed), attempts, last HTTP status and the next retry. Without an id it lists your webhooks | No |
test_webhook |
Sends one ping event now, even to a paused webhook, and returns the receiver's status and time. Not stored, not retried |
It sends a request to your receiver |
redeliver_webhook_delivery |
Sends a failed delivery again with the same X-Strait-Delivery id, so receivers that de-duplicate on it are safe |
Yes, after you confirm |
Things to ask
- "My webhook stopped firing. Show me its last deliveries and send it a test."
- "Resend every failed delivery from today." Each one previews first.
- "Which events does my Zapier webhook get?"