Skip to main content
Glama
Upload-Post

Upload-Post

Official

Get a webhook delivery

get_webhook_delivery
Read-only

Retrieve a single outgoing webhook delivery by ID, including every attempt and the exact signed JSON payload sent, to debug failures or verify what the receiver received.

Instructions

One outgoing webhook delivery with all its attempts and the exact JSON body (payload) that was signed and sent. 404 when the id is unknown, older than 7 days or belongs to another account.

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": {
      "delivery_id": "<delivery_id>"
    },
    "name": "get_webhook_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
delivery_idYes`delivery_id` from list_webhook_deliveries (the same value the receiver got in the X-Upload-Post-Delivery header).

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.23.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, lowering the bar. The description still adds real value beyond that: a 7-day retention window, account scoping, and a documented 404 outcome for unknown or expired ids. It doesn't mention rate limits or response shape, but the output schema covers the latter.

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?

Two tight sentences: the first front-loads what is returned, the second front-loads the failure conditions. No filler, no restating of the title.

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 covers the essentials: what the record contains, that the payload is the signed body, and the three conditions that produce a 404. Nothing an agent needs in order to call it correctly is missing.

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 `delivery_id` parameter is already well documented in the schema, including its origin from list_webhook_deliveries and the header. The description adds no further meaning about the parameter, so the baseline 3 applies.

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?

The description states a specific resource and scope: a single outgoing webhook delivery, with all of its attempts and the exact signed JSON body (`payload`). The singular framing plus the payload/attempts detail clearly separates it from the sibling list_webhook_deliveries, 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 Guidelines3/5

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

There is no explicit 'use this when' sentence and no naming of alternatives such as list_webhook_deliveries or redeliver_webhook. The 404 conditions (unknown id, older than 7 days, other account) do imply boundaries on when this tool will succeed, which is useful but is failure behavior rather than selection guidance.

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

Deploy Server

Other Tools