# list_webhook_deliveries

Source: https://modulify.ai/docs/mcp/webhooks/list-webhook-deliveries

Lists recent webhook delivery attempts on a site, newest first, 30 to a page.

- Title: List webhook deliveries
- Scope: `config:read`
- Access: Read only

Pass the `nextCursor` from a response back as `cursor` for the page before. It is null when there is nothing older. This is the tool for finding out why a webhook did not arrive.

Read the four states carefully: `delivered` succeeded, `pending` has not been attempted yet, `failed` is still being retried, and only `exhausted` has given up. The **Deliveries** tab shows `failed` as **Retrying** and `exhausted` as **Failed**. A delivery is tried up to 5 times before it is `exhausted`, and a test delivery is never retried.

Each delivery carries its event, state, attempts, the response `Status`, any `Error` and whether it was a `Test`. Its destination comes back as `Host` only, because a webhook URL is itself a credential. See [Webhooks](https://modulify.ai/docs/automations/webhooks#read-the-delivery-log).

## Inputs

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `projectId` | string | Yes | The site id. |
| `webhookId` | string | No | Only deliveries for this one webhook, by its id from `list_site_webhooks`. Leave it out for every webhook on the site. |
| `event` | string | No | Only deliveries of one event, `publish.succeeded`, `publish.failed` or `publish.cancelled`. Send `test` for test deliveries only, or `all` for everything, the default. |
| `cursor` | string | No | The `nextCursor` from the previous page. Leave it out for the first, newest page. |