Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_list_webhook_deliveries

List a webhook's recent deliveries to see what was sent and what the target returned. Filter by status, narrow by time window, and page through 90 days of delivery history.

Instructions

Lists a webhook's recent deliveries: what was sent and what came back.

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": {
      "webhook": "<webhook>"
    },
    "name": "tickerbot_list_webhook_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoWindow end (deliveries created up to this moment): same value grammar as `from`. A date-only value covers that whole UTC day. A timestamp is included until 2027-01-12 and exclusive from then, as everywhere else (Deprecations). `from` after `to` is a 400. See Time windows.
fromNoOnly deliveries created at or after this moment: `YYYY-MM-DD` or a UTC timestamp (`YYYY-MM-DDTHH:MM:SSZ`); a date-only value starts at the beginning of that UTC day. Delivery history is retained for 90 days; deleting a webhook deletes its delivery history with it.
limitNoPage size. Max 100.
cursorNoThe previous response's `next_cursor`. Send it with the same params as the first page (`limit` may change); a page whose params differ is a 400 naming the param.
statusNoFilter by delivery status (one or a comma list). Values: pending: Queued or mid-retry; not yet accepted by your target. delivered: Your target answered 2xx. permanent_failure: Gave up: the retry schedule ran out, or the destination refused it for good (a Discord target answered 4xx, or the mobile device is gone). A test fire is never retried.
webhookYesWebhook id.

Output Schema

NameRequiredDescriptionDefault
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
countYesThe deliveries in this page.
deliveriesYesDeliveries, newest first. Every row carries every field below; times are epoch seconds.
_advisoriesNoPresent only when the response carried a warning: `deprecated` (since, sunset_on, successor, warning; on a deprecated tool, successor names the tool to call), `rate_limit` (warning, retry_after_seconds, limit, remaining, reset_epoch_s) or `monthly_quota` (warning, limit, remaining, reset_epoch_s).
next_cursorYesOpaque token for the next page; `null` on the last page. Pass it back as `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.4.1
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor."New value: +"The previous response's `next_cursor`. Send it with the same params as the first page (`limit` may change); a page whose params differ is a 400 naming the param."
    • 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 or after this moment: `YYYY-MM-DD` or a UTC timestamp (`YYYY-MM-DDTHH:MM:SSZ`); a date-only value starts at the beginning of that UTC day. Delivery history is retained for 90 days; deleting a webhook deletes its delivery history with it."
    • removedInput schema / properties / id
      Removed value: -{
      -  "description": "Webhook id.",
      -  "type": "string"
      -}
    • 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 / status / description
      Previous value: -"Filter by delivery status."New value: +"Filter by delivery status (one or a comma list). Values: pending: Queued or mid-retry; not yet accepted by your target. delivered: Your target answered 2xx. permanent_failure: Gave up: the retry schedule ran out, or the destination refused it for good (a Discord target answered 4xx, or the mobile device is gone). A test fire is never retried."
    • removedInput schema / properties / status / enum
      Removed value: -[
      -  "pending",
      -  "delivered",
      -  "permanent_failure"
      -]
    • addedInput schema / properties / status / pattern
      Added value: +"^\\s*([pP][eE][nN][dD][iI][nN][gG]|[dD][eE][lL][iI][vV][eE][rR][eE][dD]|[pP][eE][rR][mM][aA][nN][eE][nN][tT]_[fF][aA][iI][lL][uU][rR][eE])(\\s*,\\s*([pP][eE][nN][dD][iI][nN][gG]|[dD][eE][lL][iI][vV][eE][rR][eE][dD]|[pP][eE][rR][mM][aA][nN][eE][nN][tT]_[fF][aA][iI][lL][uU][rR][eE]))*\\s*$"
    • 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: +"Window end (deliveries created up to this moment): same value grammar as `from`. A date-only value covers that whole UTC day. A timestamp is included until 2027-01-12 and exclusive from then, as everywhere else (Deprecations). `from` after `to` is a 400. See Time windows."
    • addedInput schema / properties / webhook
      Added value: +{
      +  "description": "Webhook id.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id"
      -]New value: +[
      +  "webhook"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "_advisories": {
      +      "description": "Present only when the response carried a warning: `deprecated` (since, sunset_on, successor, warning; on a deprecated tool, successor names the tool to call), `rate_limit` (warning, retry_after_seconds, limit, remaining, reset_epoch_s) or `monthly_quota` (warning, limit, remaining, reset_epoch_s).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "as_of": {
      +      "description": "Server time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "count": {
      +      "description": "The deliveries in this page.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "deliveries": {
      +      "description": "Deliveries, newest first. Every row carries every field below; times are epoch seconds.",
      +      "items": {
      +        "properties": {
      +          "attempt": {},
      +          "body_string": {},
      +          "channel": {
      +            "description": "One of: `webhook`, `discord`, `in_app`, `mobile_push`."
      +          },
      +          "created_at": {},
      +          "delivered_at": {},
      +          "event": {
      +            "description": "One of: `webhook.fired`, `events.fired`, `news.fired`."
      +          },
      +          "expires_at": {},
      +          "id": {},
      +          "last_error": {},
      +          "last_status_code": {},
      +          "next_attempt_at": {},
      +          "redelivery_of": {},
      +          "status": {
      +            "description": "One of: `pending`, `delivered`, `permanent_failure`."
      +          },
      +          "target_url": {},
      +          "test": {},
      +          "webhook_id": {}
      +        }
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "next_cursor": {
      +      "description": "Opaque token for the next page; `null` on the last page. Pass it back as `cursor`."
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "count",
      +    "next_cursor",
      +    "deliveries"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; 'what was sent and what came back' hints that request/response payloads appear in results. It does not disclose auth requirements, rate limits, or pagination semantics, though pagination is implied by the limit/cursor params and an output schema exists. Read-only safety is only inferred from the verb 'Lists'.

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 short sentence, front-loaded and free of waste. The 'what came back' clause is a slightly loose gloss but does not bloat the definition.

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?

For a six-parameter, paginated, filterable list tool with an output schema, the description is minimal. Schema and output schema cover parameters and returns, but nothing signals retention limits, auth, or when to escalate to redelivery — an agent must read structured fields to know those.

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% and the parameter docs are unusually rich (status value semantics, time-window grammar, cursor reuse rules, retention window). The description adds no parameter meaning beyond that, so the baseline applies.

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?

"Lists a webhook's recent deliveries: what was sent and what came back" gives a specific verb and resource plus a plain-language gloss of the returned payload. It does not distinguish itself from siblings like tickerbot_redeliver_webhook_delivery, but the listing operation is distinct enough to be identifiable.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance. It never routes the agent to tickerbot_redeliver_webhook_delivery for retrying a failed delivery, nor states prerequisites such as needing a valid webhook id. The 90-day retention note lives in the schema, not as usage context here.

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