mcp-server

tickerbot_list_webhook_deliveries

Recent deliveries for one webhook — what was sent, and what came back.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Webhook id.
`to`	No	Only deliveries created at/before this moment — same value grammar as `from`. A date-only value means through the end of that UTC day. `from` after `to` is a 400.
`from`	No	Only deliveries created at/after this moment — epoch seconds, epoch milliseconds (13+ digits), or an ISO datetime (`since` is accepted as an alias). Delivery history is retained for 90 days; deleting a webhook deletes its delivery history with it.
`limit`	No	Page size. Max 100.
`cursor`	No	Opaque cursor.
`status`	No	Filter by delivery status.

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	Yes	Server time this response was assembled (ISO 8601).
`count`	Yes	Rows in this page.
`deliveries`	Yes	Attempts, newest first: status, attempt, response code, error, and `body_string` — the exact JSON POSTed.
`next_cursor`	Yes	Opaque token for the next page; `null` on the last page. Pass it back as `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "as_of": {
+      "description": "Server time this response was assembled (ISO 8601).",
+      "type": "string"
+    },
+    "count": {
+      "description": "Rows in this page.",
+      "type": "number"
+    },
+    "deliveries": {
+      "description": "Attempts, newest first: status, attempt, response code, error, and `body_string` — the exact JSON POSTed.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Opaque token for the next page; `null` on the last page. Pass it back as `cursor`.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "as_of",
+    "count",
+    "next_cursor",
+    "deliveries"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedSep 17, 2026

changedInput schema / properties / from / description

Previous value: -"Only deliveries created at/after this moment — epoch seconds, epoch milliseconds (13+ digits), or ISO datetime. (90-day retention on every plan.)"New value: +"Only deliveries created at/after this moment — epoch seconds, epoch milliseconds (13+ digits), or an ISO datetime (`since` is accepted as an alias). Delivery history is retained for 90 days; deleting a webhook deletes its delivery history with it."

addedInput schema / properties / limit / default
```
Added value: +50
```

changedInput schema / properties / limit / description

Previous value: -"Page size. Max 100. Default 50."New value: +"Page size. Max 100."

changedInput schema / properties / to / description

Previous value: -"Only deliveries created at/before this moment — same value grammar as `from`; a date-only value means through the end of that UTC day."New value: +"Only deliveries created at/before this moment — same value grammar as `from`. A date-only value means through the end of that UTC day. `from` after `to` is a 400."

Changed1 schema field changedAug 8, 2026

addedInput schema / properties / to

Added value: +{
+  "description": "Only deliveries created at/before this moment — same value grammar as `from`; a date-only value means through the end of that UTC day.",
+  "type": "string"
+}

Changed1 schema field changedAug 8, 2026

changedInput schema / properties / from / description

Previous value: -"Only deliveries created at/after this moment — epoch seconds or ISO datetime. (90-day retention on every plan.)"New value: +"Only deliveries created at/after this moment — epoch seconds, epoch milliseconds (13+ digits), or ISO datetime. (90-day retention on every plan.)"

Changed1 schema field changedAug 7, 2026

addedInput schema / properties / from

Added value: +{
+  "description": "Only deliveries created at/after this moment — epoch seconds or ISO datetime. (90-day retention on every plan.)",
+  "type": "string"
+}

AddedJun 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It communicates a read-style listing operation and that each delivery includes the sent payload and the response, which is useful. It does not disclose side effects, auth requirements, rate limits, or retention details, though 'recent' hints at a time-bounded result.

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 a single front-loaded sentence with no filler. Every phrase earns its place: 'recent', 'for one webhook', and 'what was sent, and what came back' all help an agent select and expect the tool's behavior.

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?

The rich input schema covers the date filters, pagination, default, and status enum, and the output schema covers return shape, so the short description does not need to restate those. A brief note about read-only semantics or when to first call list_webhooks would round it out, but the core invocation context is present.

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 100%, so the input schema already documents every parameter. The description adds little parameter-specific meaning beyond 'one webhook' mapping to the required id. This is the baseline case where the schema does the heavy lifting.

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 clearly identifies the resource as 'deliveries for one webhook', which distinguishes it from sibling list tools such as tickerbot_list_webhooks. The phrase 'what was sent, and what came back' also sets expectations about the returned delivery history. It is clear but does not explicitly state the 'list' verb or name an alternative tool.

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?

The phrasing 'for one webhook' implies the correct use case: an agent should call this when it already has a webhook id and wants delivery history. However, the description does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools for inspecting webhook configuration.

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

All mcp-server 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.