Social Fetch

List deliveries for a webhook endpoint

webhookEndpoints_deliveries_list

Read-only

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.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`after`	No
`limit`	No
`cursor`	No
`status`	No
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`conversation_id`	No	Echo 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.

Changed4 schema fields changedSep 5, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo 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.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "id"
-]New value: +[
+  "id",
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedAug 4, 2026

addedInput schema / properties / cursor

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

AddedJul 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate a safe read operation (readOnlyHint=true), and the description adds useful behavioral detail: `cursor` is opaque, requiring continuation as provided, and `after` switches to oldest-first tail ordering. These are non-obvious behaviors not fully expressed by the schema alone.

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?

The description is two sentences: the first states the operation clearly, the second lists the pagination controls and the tail-mode use case. Every sentence adds distinct value, and the most important information is front-loaded.

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

Completeness3/5

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

The description covers pagination and ordering behavior well, but gaps remain: the `id` parameter's role is implied rather than stated, the `status` filter is not mentioned, and with no output schema, the delivery-attempt response shape is not described. It is adequate for a straightforward paginated list call but incomplete for an 8-parameter tool with no output schema.

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?

The description adds meaning for `limit`, `cursor`, and `after`, clarifying pagination and the special tail mode. However, schema description coverage is low (38%), and the critical required `id` parameter is not explained (e.g., it is the webhook endpoint ID), and the `status` filter is undocumented in the description.

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 verb and resource: 'List delivery attempts for a webhook endpoint.' This clearly differentiates the tool from siblings like webhookEndpoints_get, webhookEndpoints_list, and webhookDeliveries_redeliver, which concern endpoints or redelivery rather than listing delivery attempts.

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

Usage Guidelines4/5

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

The description gives clear context for when the tool is appropriate: listing delivery attempts for a webhook endpoint, with special mention of using `after` for oldest-first tail mode aimed at listeners. It does not explicitly exclude alternatives, but there is no close sibling that performs the same listing function, so the context is sufficient.

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

All Social Fetch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

List deliveries for a webhook endpoint

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources