Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_list_webhooks

List every webhook on your account newest first, filter by active or disabled status, and page through results for subscription review.

Instructions

Lists every webhook on your account, newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tickerbot_list_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 status: `active`, `disabled` or both as a comma list. A webhook is always one of the two (`disabled` covers a user pause, the automatic disable after deliveries have kept failing for 72 hours with none getting through, and the automatic disable of a trigger that cannot run; `disabled_reason` on each record says which: `user_disabled`, `delivery_failure`, `evaluation_failure`, `plan_downgrade` or `subscription_canceled`). Omit for all. Values: active: The subscription is live and being evaluated. disabled: Turned off; `disabled_reason` says why. `user_disabled`: you turned it off. `delivery_failure`: deliveries kept failing for 72 hours with none getting through. `evaluation_failure`: its rule can no longer run, such as when a signal it reads was removed or its universe was deleted. `plan_downgrade`: the account moved to a plan with fewer webhooks, and the newest beyond the new limit were turned off. `subscription_canceled`: the paid subscription ended. Turn it back on with `PATCH /v2/webhooks/{webhook}` and `enabled: true`.

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 webhooks in this page.
webhooksYesYour subscriptions, newest first, each with its `subscription_origin` and health fields. `signing_secret` is stripped: it is shown only on create.
_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. Changed7 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."
    • 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 status: `active` or `disabled`. Omit for all."New value: +"Filter by status: `active`, `disabled` or both as a comma list. A webhook is always one of the two (`disabled` covers a user pause, the automatic disable after deliveries have kept failing for 72 hours with none getting through, and the automatic disable of a trigger that cannot run; `disabled_reason` on each record says which: `user_disabled`, `delivery_failure`, `evaluation_failure`, `plan_downgrade` or `subscription_canceled`). Omit for all. Values: active: The subscription is live and being evaluated. disabled: Turned off; `disabled_reason` says why. `user_disabled`: you turned it off. `delivery_failure`: deliveries kept failing for 72 hours with none getting through. `evaluation_failure`: its rule can no longer run, such as when a signal it reads was removed or its universe was deleted. `plan_downgrade`: the account moved to a plan with fewer webhooks, and the newest beyond the new limit were turned off. `subscription_canceled`: the paid subscription ended. Turn it back on with `PATCH /v2/webhooks/{webhook}` and `enabled: true`."
    • removedInput schema / properties / status / enum
      Removed value: -[
      -  "active",
      -  "disabled"
      -]
    • addedInput schema / properties / status / pattern
      Added value: +"^\\s*([aA][cC][tT][iI][vV][eE]|[dD][iI][sS][aA][bB][lL][eE][dD])(\\s*,\\s*([aA][cC][tT][iI][vV][eE]|[dD][iI][sS][aA][bB][lL][eE][dD]))*\\s*$"
    • 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)."
      +    },
      +    "count": {
      +      "description": "The webhooks in this page."
      +    },
      +    "next_cursor": {
      +      "description": "Opaque token for the next page; `null` on the last page. Pass it back as `cursor`."
      +    },
      +    "webhooks": {
      +      "description": "Your subscriptions, newest first, each with its `subscription_origin` and health fields. `signing_secret` is stripped: it is shown only on create."
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "count",
      +    "next_cursor",
      +    "webhooks"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add two real behavioral facts — the result is account-scoped and ordered newest-first — but says nothing about pagination, whether the list is complete or truncated, or any permission requirements, all of which matter for a paged list endpoint.

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?

A single eleven-word sentence with the scope and ordering front-loaded and zero filler. Nothing needs to be trimmed.

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?

An output schema exists and the input schema is exhaustive, so return values and parameters need no prose. However, for a listing endpoint surrounded by get/list/delete/enable webhook siblings, the description is too thin on routing and pagination behavior to be fully self-sufficient.

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 input schema is fully described (100% coverage), including limit paging, the cursor-must-match-first-page rule, and the active/disabled filter with all disabled_reason values. The description adds no parameter meaning beyond that, so the baseline of 3 is appropriate.

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?

States a specific verb ("Lists") and resource ("every webhook on your account") plus the ordering ("newest first"), so an agent knows exactly what it retrieves. It does not name or contrast the adjacent siblings (tickerbot_get_webhook for a single record, tickerbot_list_webhook_deliveries for delivery history), leaving differentiation to inference.

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?

The description gives no when-to-use guidance and no exclusions. It never says to prefer tickerbot_get_webhook when you already have a webhook ID, or tickerbot_list_webhook_deliveries when you want delivery attempts rather than subscription records.

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