Skip to main content
Glama

list_webhook_deliveries

Read-only

Recent delivery attempts for one webhook (status, attempts, last error) — for debugging a Zap that stopped firing.

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

Input Schema

NameRequiredDescriptionDefault
webhookIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful return-shape context (status, attempts, last error) and implies a recency window, but says nothing about how many deliveries are returned, ordering, pagination, or what happens for an unknown webhookId.

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?

A single sentence with zero filler: resource scope first, returned fields in parentheses, then the diagnostic purpose. Nothing is buried or repeated.

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?

For a read-only single-parameter list tool with no output schema, the description usefully names the visible fields and the debugging scenario. The only real gap is volume/pagination behavior, which matters for any list endpoint but is not strictly needed to call it correctly.

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 0%, so schema documentation does not compensate, but the single parameter is named webhookId and the description clarifies it selects exactly 'one webhook'. It adds no syntax, format, or sourcing guidance for that ID beyond the name itself, which is near the minimum for a one-parameter tool.

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 resource ('Recent delivery attempts for one webhook'), scopes it to a single webhook, and enumerates the returned fields (status, attempts, last error). The diagnostic framing ('for debugging a Zap that stopped firing') separates it clearly from siblings like send_test_webhook or create_webhook.

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 an explicit use case — troubleshooting a Zap that stopped firing — which is a concrete trigger for calling this rather than send_test_webhook or list_ai_run_history. It stops short of naming an alternative or stating when-not to use it, so it lacks full routing guidance.

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.