Skip to main content
Glama

List webhook deliveries

webhooks_list_deliveries
Read-only

List a webhook's delivery attempts with event, status, attempt count, and response code, newest first; paginate using limit and the previous page's nextCursor.

Instructions

List one webhook's delivery attempts (event, status, attempts, response code), newest first. Paginate with limit and the previous page's nextCursor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "webhookId": "<webhookId>"
    },
    "name": "webhooks_list_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return per page (1–100, default 20).
cursorNoOpaque — pass the previous response's `nextCursor` verbatim to fetch the next page. Never construct or parse this value yourself; its shape is not part of the public contract and may change.
webhookIdYesA Klappay webhook id (`wh_` followed by letters and digits).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral detail — newest-first ordering and the fields available per delivery — but omits retention limits, rate limits, or empty-result behavior; a 3 is appropriate given the annotations carry the safety burden.

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?

Two tight sentences with no filler; the resource and returned fields are front-loaded, followed by pagination instructions. Appropriate for a simple read-only list tool, though the parenthetical field list is slightly terse.

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 no output schema, the description carries the return-value burden and does so by enumerating delivery fields and ordering. Pagination is covered via limit and nextCursor. For a three-parameter read-only list tool, the definition is nearly complete, missing only edge-case behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by pairing limit with nextCursor as the pagination contract and clarifying that the cursor comes from the previous page. That is a small value-add beyond the schema's per-parameter descriptions.

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 and resource — listing one webhook's delivery attempts — and names the fields returned (event, status, attempts, response code) plus ordering (newest first). An agent can distinguish it from webhooks_list, which lists webhooks rather than deliveries, though no sibling is explicitly named.

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 description explains pagination mechanics (limit and previous page's nextCursor) but gives no explicit when-to-use guidance versus siblings such as webhooks_list or webhooks_retry_delivery. Usage context is implied by the resource name rather than stated.

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