Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List deliveries for a webhook endpoint

webhookEndpoints_deliveries_list
Read-onlyIdempotent

List webhook endpoint delivery attempts with limit and cursor pagination, plus an optional after timestamp for oldest-first tailing, so you can inspect recent or incoming webhook events.

Instructions

List delivery attempts for a webhook endpoint. Supports limit, opaque cursor continuation, and optional after (ISO timestamp) to enter oldest-first tail mode for listeners.

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

Input Schema

NameRequiredDescriptionDefault
idYes
afterNo
limitNo
cursorNo
statusNo
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value with the opaque-cursor and oldest-first tail-mode semantics, but omits default result ordering, what the `status` filter does to the result set, and does not reinforce the schema's constraint that no parallel calls should be issued before conversation_id is known.

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 sentences, zero filler, and the core purpose is front-loaded before the pagination modifiers. Nothing needs trimming.

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?

For an 8-parameter tool with 38% schema coverage and no output schema, the description leaves significant gaps: the `status` filter and the required `id` are unmentioned, and with no output schema the agent has no idea what a delivery record contains (status, timestamps, response codes). The low schema coverage means the description should be doing more work than it does.

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 only 38%, so the description must carry more of the load. It explains cursor as 'opaque continuation' (genuinely additive) but only name-drops `limit` and `after` without format or boundary detail, and never mentions the required `id` endpoint identifier or the `status` enum filter at all.

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 states a specific verb and resource ('List delivery attempts for a webhook endpoint'), which cleanly separates it from the sibling mutations such as webhookDeliveries_redeliver. It does not name an alternative tool or explain how it differs from webhookEndpoints_get, so it stops short of full sibling differentiation.

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 a usage hint in the 'after' clause ('enter oldest-first tail mode for listeners'), which tells the agent when that parameter mode is appropriate. However, there is no stated guidance on when to list versus redeliver, no prerequisites, and no explanation of when to page with `cursor` instead of using `after`.

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