Skip to main content
Glama

List a webhook's deliveries

list_webhook_deliveries
Read-onlyIdempotent

The latest 50 deliveries of one of the user's webhooks, newest first: each event's id and type, whether it was delivered, is waiting or being retried, failed or expired, how many attempts it took, and what the address answered on the last one. Use it when the user asks why their address did or did not get a message. The messages themselves are not shown.

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

Input Schema

NameRequiredDescriptionDefault
webhook_idYesFrom list_webhooks.

Output Schema

NameRequiredDescriptionDefault
hostNo
deliveriesNo
webhook_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds behavior they cannot express: a hard cap of 50 records, newest-first ordering, the full status taxonomy (delivered/waiting/retried/failed/expired), attempt counts, and the last response from the endpoint. It also explicitly states a content boundary — message payloads are not shown — which prevents an agent from promising data this tool cannot return.

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?

Front-loaded with what is returned and its ordering, then the usage trigger, then the limitation. Every clause carries distinct information — the status list is dense but is the substance of the answer the user is asking for, and nothing is redundant with the annotations or schema.

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

Completeness5/5

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

For a single-parameter read tool with an output schema, the description supplies everything else an agent needs: record count, ordering, field meanings, the diagnostic use case, and the exclusion of message bodies. No behavioral question likely to arise before invocation is left open.

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% and the single parameter is already documented as coming 'From list_webhooks.' The description implies single-webhook scoping ('one of the user's webhooks') but adds no format, id-source, or validation detail beyond the schema. Baseline 3 applies when the schema carries the parameter semantics.

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

Purpose5/5

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

States a specific verb and resource (list a webhook's deliveries) plus the exact scope: latest 50, newest first. It also enumerates what each record contains, so an agent can distinguish this from list_webhooks, which returns the webhooks themselves rather than their delivery history.

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

Usage Guidelines4/5

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

Gives a concrete triggering situation: 'Use it when the user asks why their address did or did not get a message.' That is real when-to-use guidance, though it names no explicit alternative for the case where the user wants the webhook configuration itself (list_webhooks).

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.

Resources