Skip to main content
Glama

List Webhook Deliveries

list_webhook_deliveries
Read-onlyIdempotent

Read recent delivery receipts for an event webhook: status, attempts, response code and retry time. Follow nextCursor as cursor for older receipts. A delivered receipt means the endpoint returned 2xx. Read-only.

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": {
      "event_id": "<event_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "list_webhook_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
event_idYes
webhook_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds genuine semantic context beyond them: the definition of a delivered receipt (endpoint returned 2xx), the fields returned, and the backward direction of cursor paging. It does not mention retention windows or ordering beyond 'recent', which keeps it below a 5.

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

Conciseness5/5

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

Three short sentences with zero filler: purpose and returned fields first, then pagination mechanics, then the semantic definition of 'delivered'. Everything is front-loaded and each sentence adds new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no output schema, the description does well to enumerate returned fields and explain paging. But with zero schema description coverage on four parameters and no mention of limits or default page size, an agent still has to guess at request shape.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must carry the load. It explains the cursor parameter's purpose and direction, but says nothing about event_id, webhook_id, or limit (including its 100 maximum), leaving half the parameters undocumented anywhere.

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?

The description opens with a specific verb and resource ('Read recent delivery receipts for an event webhook') and enumerates the returned fields (status, attempts, response code, retry time), so the agent knows exactly what this tool produces. It does not explicitly position itself against siblings such as list_event_webhooks or replay_webhook_delivery, which keeps it from a 5.

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?

It gives concrete pagination guidance ('Follow nextCursor as cursor for older receipts'), which is real when-to-use information for iterating. However, it never says when to prefer this tool over replay_webhook_delivery or how it relates to listing webhooks, and offers no exclusions, so guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.