Skip to main content
Glama

Realtime: Get delivery logs

webhook_get_delivery_logs
Read-onlyIdempotent

Inspect recent webhook delivery attempts for this destination. Use when an agent/n8n receiver did not wake or a test event was not observed. Use to investigate whether a delivery was attempted.

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": {
      "destination_id": "<destination_id>",
      "limit": "<limit>"
    },
    "name": "webhook_get_delivery_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYes
destination_idYesNilyo webhook destination ID returned by webhook_create_destination/webhook_list_destinations. Never use the remote webhook endpoint ID directly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / destination_id / description
      Previous value: -"Nilyo webhook destination ID returned by webhook_create_destination/webhook_list_destinations. Never use the Unipile endpoint ID directly."New value: +"Nilyo webhook destination ID returned by webhook_create_destination/webhook_list_destinations. Never use the remote webhook endpoint ID directly."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds useful diagnostic framing (this answers "was a delivery even attempted?") but says nothing about what a log entry contains, how far back "recent" reaches, or whether failures vs successes are both included.

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?

Three short sentences, front-loaded with the purpose before the diagnostic use cases. The second and third sentences overlap somewhat ("did not wake / test event not observed" vs "whether a delivery was attempted") but nothing is wasted enough to harm usability.

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?

With no output schema and only two parameters, the description should tell the agent what the returned log entries look like (status, timestamps, response codes) and how many are returned. It conveys the investigative intent well but leaves the return shape entirely unspecified.

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 coverage is 50%: destination_id is well documented in the schema, but limit (default 20, max 100) has no description anywhere. The description never mentions the limit or the number of attempts returned, so it fails to compensate for the undocumented half of the parameters.

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: "Inspect recent webhook delivery attempts for this destination." This is clearly separable from sibling tools like webhook_get_destination (destination config) and webhook_list_destinations (enumeration), so an agent can pick it without opening the schema.

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 concrete triggering conditions: an agent/n8n receiver did not wake, or a test event was not observed. It does not name an alternative tool (e.g. webhook_get_test_guide) or state when not to use it, which keeps it short of a 5.

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.