READ

list_webhook_endpoints

List the outbound webhook endpoints registered for the token's team, paginated, with their health counters. Secrets are never returned.

List the outbound webhook endpoints registered for the token's team, newest first, each with its target, the events it receives, whether it is active and the health counters the application shows. Useful for sanity-checking integrations after a suspected outage, before reading the delivery log.

Endpoint secrets are never returned by this tool. They are surfaced only at the moment of creation or rotation, by create_webhook_endpoint and rotate_webhook_endpoint_secret.

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

Runs the same action as

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

Read-only

It reads and never changes anything.

Arguments

limitintegeroptional

Endpoints per page (1..100, default 25).

min1max100
pageintegeroptional

1-indexed page number.

min1

What it returns

{  "data": [    {      "id": "c62a08f4-1b7d-4e35-9860-a37f5d21e0b9",      "name": "Delivery board",      "url": "https://hooks.example.test/zusegenius",      "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",      "events": ["project.created", "project.status_changed"],      "is_active": true,      "disabled_at": null,      "allowed_ips": null,      "failure_count": 0,      "consecutive_failures": 0,      "last_success_at": "2026-10-25T10:05:00+00:00",      "last_failure_at": null,      "created_at": "2026-10-01T10:05:00+00:00",      "updated_at": "2026-10-25T10:05:00+00:00"    }  ],  "meta": { "page": 1, "limit": 25, "total": 3, "has_more": false }}

How it fails

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks webhook-endpoint:view-any.

How is this guide?

Last updated on