Skip to main content
Glama
Upload-Post

Upload-Post

Official

Redeliver a webhook

redeliver_webhook

Resend a past webhook delivery to the currently configured URL with the same body and a new delivery ID; show a preview, get approval before sending, and use only for missed events.

Instructions

Send a past webhook delivery again, now, with the same body, to the webhook URL configured TODAY for that account or profile. It goes out as a new delivery with its own delivery_id (its redelivery_of and the X-Upload-Post-Redelivery-Of header name the original), and is retried like any other if it fails. The receiver gets the event a second time, so only redeliver events it missed. 409 when there is nowhere to send it (reason: webhook_removed, event_unsubscribed, blocked_url); 404 when the delivery is unknown or older than 7 days. Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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

Input Schema

NameRequiredDescriptionDefault
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
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.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the body is reused but the URL is the one configured today, that a new delivery_id is minted with `redelivery_of` and the X-Upload-Post-Redelivery-Of header, that failures are retried, and that the receiver sees the event twice. The 409 reason values and 7-day 404 window are concrete behavioral facts the annotations cannot convey.

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?

Front-loaded with the core action and semantics, then error codes, then the approval requirement. Dense but nearly every clause carries information; the only cost is that it reads as one long paragraph rather than separated blocks.

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 non-idempotent, open-world mutation with an output schema already present, the description covers the side effects, the approval gate, the failure modes, and the retry behavior. Nothing an agent needs to call it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains the two-step preview/confirm protocol that gives `confirmed` its purpose and clarifies that `delivery_id` is the value the receiver saw in the X-Upload-Post-Delivery header. That is more than the schema states.

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 ('Send a past webhook delivery again, now') and immediately pins down the semantics: same body, current URL, new delivery_id. This clearly separates it from get_webhook_delivery and list_webhook_deliveries, which only read deliveries.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule ('only redeliver events it missed'), a mandatory approval workflow (call without `confirmed` for a preview, then repeat with `confirmed: true`), and the exact conditions that produce 409 and 404. An agent has no ambiguity about when or how to invoke it.

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