Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Manually redeliver a webhook delivery

webhookDeliveries_redeliver
Destructive

Queue an asynchronous manual redelivery for a single webhook delivery attempt, letting you retry failed or missed notifications.

Instructions

Queue a manual redelivery for one delivery attempt (async).

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": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "webhookDeliveries_redeliver"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/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, so the safety profile is covered. The description's sole addition is '(async)', which usefully warns that the call only enqueues work and that the redelivery result will not be returned synchronously. It stops short of stating what the async operation does to the original attempt, whether a duplicate attempt is created, or what errors arise for an already-succeeded delivery.

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?

A single front-loaded sentence with no filler, and the '(async)' qualifier sits at the end where it is easy to catch. It is efficient, though its brevity is part of why behavioral coverage is thin.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, non-idempotent mutation with three required parameters and no output schema, so the description should explain the outcome of redelivery and any state it alters. Instead it offers only 'async', leaving an agent unsure whether the original attempt is retried in place, duplicated, or what happens on an already-delivered attempt.

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 75% and the context/llm_model/conversation_id parameters are fully documented in the schema. The description contributes only the implied meaning of 'id' as the identifier of a single delivery attempt; it adds nothing about the metadata parameters. Baseline 3 is appropriate since the schema carries most of the weight.

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?

The description names a specific verb ('Queue a manual redelivery') and resource ('one delivery attempt'), making the action unambiguous and distinct from sibling reads like webhookEndpoints_deliveries_list or webhookEndpoints_test. It does not explicitly contrast itself with those siblings, which keeps it just short of a 5.

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?

Usage is only implied: 'manual redelivery' suggests the caller should reach for this when a prior delivery attempt failed and needs to be retried by hand. There is no stated precondition (e.g., delivery must exist/must have failed) and no explicit pointer to alternative ways of retrying delivery, such as webhookEndpoints_test.

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