Proof Holdings

list_webhook_deliveries

Read-only

List webhook delivery attempts with pagination and filtering. Shows delivery status, response codes, and timestamps.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.

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": "list_webhook_deliveries"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number
`limit`	No	Items per page
`status`	No	Filter by delivery status
`event_type`	No	Filter by event type (e.g. verification.completed)
`profile_id`	No	Only this sub-account's deliveries
`endpoint_id`	No	Only deliveries to this webhook endpoint
`verification_request_id`	No	Only deliveries for this verification request

Output Schema

Name	Required	Description	Default
`data`	Yes
`pagination`	Yes	Pagination info in list responses

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 2, 2026

addedInput schema / properties / endpoint_id

Added value: +{
+  "description": "Only deliveries to this webhook endpoint",
+  "pattern": "^[0-9a-fA-F]{24}$",
+  "type": "string"
+}

addedInput schema / properties / profile_id

Added value: +{
+  "description": "Only this sub-account's deliveries",
+  "pattern": "^[0-9a-fA-F]{24}$",
+  "type": "string"
+}

addedInput schema / properties / verification_request_id

Added value: +{
+  "description": "Only deliveries for this verification request",
+  "pattern": "^[0-9a-fA-F]{24}$",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "attempts": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "delivered_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "endpoint_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "error_message": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "event_type": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "last_attempt_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "max_attempts": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "next_retry_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "profile_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "response_status": {
+            "anyOf": [
+              {
+                "maximum": 9007199254740991,
+                "minimum": -9007199254740991,
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "status": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "verification_request_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "verification_request_id",
+          "endpoint_id",
+          "profile_id",
+          "event_type",
+          "url",
+          "status",
+          "attempts",
+          "max_attempts",
+          "last_attempt_at",
+          "next_retry_at",
+          "delivered_at",
+          "response_status",
+          "error_message",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "additionalProperties": {},
+      "description": "Pagination info in list responses",
+      "properties": {
+        "limit": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "page": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "total": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "total_pages": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "pagination"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```
First observedSep 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

readOnlyHint=true already declares the safety profile, but the description adds genuinely non-obvious behavior: the result set is paginated and filtered, and each record carries status/response code/timestamp. The ACCESS block is the most valuable part, explicitly warning that start_login does NOT unlock this tool and that re-authentication is required. It does not mention rate limits or default page size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The capability sentence is front-loaded and dense: pagination, filtering, and returned fields in two sentences. The ACCESS block costs some space but earns it by preventing a failed auth loop. Minor redundancy between 'Shows delivery status, response codes, and timestamps' and the output schema.

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 seven optional params, full schema coverage, an output schema, and readOnlyHint, the definition covers what remains: auth prerequisites and the shape of the listing. The one gap is sibling disambiguation against get_webhook_delivery and get_webhook_stats, which an agent must infer.

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 description coverage is 100%, with each of the seven filters documented inline including the enum values and the ObjectId patterns, so the schema does the heavy lifting. The description only restates 'pagination and filtering' generically and adds no filter semantics beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: list webhook delivery attempts, with the scope of pagination and filtering. It also names what the records contain (status, response codes, timestamps). It stops short of differentiating itself from the single-record sibling get_webhook_delivery or from get_webhook_stats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The filtering scope implies when this is the right tool, and the ACCESS block gives a real prerequisite (authenticate via /mcp; start_login does not work here). However, it never routes the agent to alternatives such as get_webhook_delivery for a single attempt, get_webhook_stats for aggregates, or list_webhook_endpoints for endpoint configuration.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Proof Holdings 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.