Skip to main content
Glama

Retry webhook delivery

webhooks_retry_delivery
Destructive

Re-send a missed or failed webhook delivery to its endpoint so the receiving system processes the event again.

Instructions

Re-send one past webhook delivery to its endpoint now. The receiving system will process the event again.

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>",
      "deliveryId": "<deliveryId>"
    },
    "name": "webhooks_retry_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookIdYesA Klappay webhook id (`wh_` followed by letters and digits).
deliveryIdYesA Klappay webhook delivery id (`ev_` followed by letters and digits).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true; the description adds the meaningful consequence that the receiving system will process the event again, which explains the duplicate-processing risk. It does not say whether a new delivery record is created, whether the original is replaced, or whether retries are rate-limited.

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 short sentences, zero waste, with the action front-loaded and the side effect immediately after.

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 two-parameter mutation with no output schema and full annotation coverage, the description supplies the essential action and its external side effect. Only the return value and the fate of the original delivery record are left unstated.

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 coverage is 100% and both parameters carry format descriptions, so the schema does the heavy lifting. The description only implies that a single delivery is targeted, adding no meaning beyond the schema.

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

Purpose4/5

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

States a specific verb and resource ("Re-send one past webhook delivery to its endpoint") with clear scope: exactly one, already-existing delivery, sent immediately. An agent can distinguish this from listing deliveries, though no sibling is named explicitly.

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?

"one past webhook delivery" implies the precondition that a delivery must already exist and be identified, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g., listing deliveries first to find the id).

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