Skip to main content
Glama

tickerbot_update_webhook

Edit a webhook in place — send only the fields you want to change. The trigger and channel are immutable — delete and re-create to change what fires or where it delivers. Unknown fields are a 400.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWebhook id.
nameNoNew display name. Non-empty, max 80 characters.
cadenceNoEvaluation cadence. A user preference — never gated. Event triggers deliver on ingest — only `realtime` is accepted on them (400 otherwise).
enabledNo`false` disables the webhook (status → `disabled`). `true` is a no-op unless disabled, in which case use `POST /v2/webhooks/{id}/enable` instead.
target_urlNoNew https:// delivery URL (webhook channel only — a Discord/mobile subscription 400s here). `null` or empty switches to in-app delivery; `status` is untouched — a disabled webhook stays disabled until `POST /v2/webhooks/{id}/enable` (the only path that re-checks your account's webhook cap).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesThe stored predicate. Custom signals appear expanded: the SQL is frozen at creation.
idYesThe webhook id — `wh_…`, the handle for every other call on this record.
dirYesSort direction for that list; `null` means the default (`desc`).
nameYesYour label for the subscription.
as_ofYesServer time this response was assembled (ISO 8601).
orderYesSort signal for the payload row list; `null` means the evaluator default (`market_cap`).
fieldsYesExtra signals carried on each fired match row; `null` means the standard set.
sourceYesWhich API version created the record; `v2` for anything you create today.
statusYes`active` or `disabled`. Auto-disable follows repeated delivery failure.
cadenceYesHow often the trigger is evaluated — `realtime`, `hourly`, or `nyse_open`.
channelYesWhere deliveries go: `webhook`, `discord`, `in_app`, or `mobile_push`.
event_qNoEvent-trigger webhooks only: the payload filter, or `null`.
rule_idYesLegacy link to a v1 alert rule; `null` on everything created through v2.
deliveryYesLegacy alias of `channel`, kept aligned for older readers.
created_atYesCreation timestamp.
last_errorNoThe last evaluation error; `null` on a healthy hook. The answer to "why is my webhook not firing?".
last_firedYesWhen a delivery last went out; `null` if it never has.
target_urlYesYour HTTPS endpoint; `null` on every channel except `webhook`.
updated_atYesLast modification timestamp.
event_kindsNoEvent-trigger webhooks only: the kinds subscribed (`split`, `dividend`, `insider`, `analyst`, `earnings`).
universe_idYesUniverse the trigger is scoped to, or `null` for the whole market.
next_eval_atYesWhen the evaluator will next consider this subscription.
trigger_kindNoEvent-trigger webhooks only: `event`.
event_tickersNoEvent-trigger webhooks only: the symbols the trigger is scoped to, or `null` for the universe / whole market.
last_match_setYesTickers matching at the last evaluation — the set the next run is diffed against, which is what makes firing edge-triggered.
last_evaluated_atYesWhen it was last evaluated; `null` until the first run.
last_eval_error_atNoWhen the last evaluation error happened; `null` on a healthy hook.
subscription_originYesWhich door created it — `type` (`ticker`/`signal`/`scan`/`event`), its `ref`, and the `condition` in display form.
last_predicate_valueYesThe trigger's value at the last evaluation; `null` until it has run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "as_of": {
      +      "description": "Server time this response was assembled (ISO 8601).",
      +      "type": "string"
      +    },
      +    "cadence": {
      +      "description": "How often the trigger is evaluated — `realtime`, `hourly`, or `nyse_open`.",
      +      "type": "string"
      +    },
      +    "channel": {
      +      "description": "Where deliveries go: `webhook`, `discord`, `in_app`, or `mobile_push`.",
      +      "type": "string"
      +    },
      +    "created_at": {
      +      "description": "Creation timestamp.",
      +      "type": "number"
      +    },
      +    "delivery": {
      +      "description": "Legacy alias of `channel`, kept aligned for older readers.",
      +      "type": "string"
      +    },
      +    "dir": {
      +      "description": "Sort direction for that list; `null` means the default (`desc`).",
      +      "type": "string"
      +    },
      +    "event_kinds": {
      +      "description": "Event-trigger webhooks only: the kinds subscribed (`split`, `dividend`, `insider`, `analyst`, `earnings`).",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "event_q": {
      +      "description": "Event-trigger webhooks only: the payload filter, or `null`.",
      +      "type": "string"
      +    },
      +    "event_tickers": {
      +      "description": "Event-trigger webhooks only: the symbols the trigger is scoped to, or `null` for the universe / whole market.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "fields": {
      +      "description": "Extra signals carried on each fired match row; `null` means the standard set.",
      +      "type": "string"
      +    },
      +    "id": {
      +      "description": "The webhook id — `wh_…`, the handle for every other call on this record.",
      +      "type": "string"
      +    },
      +    "last_error": {
      +      "description": "The last evaluation error; `null` on a healthy hook. The answer to \"why is my webhook not firing?\".",
      +      "type": "string"
      +    },
      +    "last_eval_error_at": {
      +      "description": "When the last evaluation error happened; `null` on a healthy hook.",
      +      "type": "number"
      +    },
      +    "last_evaluated_at": {
      +      "description": "When it was last evaluated; `null` until the first run.",
      +      "type": "number"
      +    },
      +    "last_fired": {
      +      "description": "When a delivery last went out; `null` if it never has.",
      +      "type": "number"
      +    },
      +    "last_match_set": {
      +      "description": "Tickers matching at the last evaluation — the set the next run is diffed against, which is what makes firing edge-triggered.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "last_predicate_value": {
      +      "description": "The trigger's value at the last evaluation; `null` until it has run.",
      +      "type": "string"
      +    },
      +    "name": {
      +      "description": "Your label for the subscription.",
      +      "type": "string"
      +    },
      +    "next_eval_at": {
      +      "description": "When the evaluator will next consider this subscription.",
      +      "type": "number"
      +    },
      +    "order": {
      +      "description": "Sort signal for the payload row list; `null` means the evaluator default (`market_cap`).",
      +      "type": "string"
      +    },
      +    "q": {
      +      "description": "The stored predicate. Custom signals appear expanded: the SQL is frozen at creation.",
      +      "type": "string"
      +    },
      +    "rule_id": {
      +      "description": "Legacy link to a v1 alert rule; `null` on everything created through v2.",
      +      "type": "string"
      +    },
      +    "source": {
      +      "description": "Which API version created the record; `v2` for anything you create today.",
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "`active` or `disabled`. Auto-disable follows repeated delivery failure.",
      +      "type": "string"
      +    },
      +    "subscription_origin": {
      +      "description": "Which door created it — `type` (`ticker`/`signal`/`scan`/`event`), its `ref`, and the `condition` in display form.",
      +      "type": "object"
      +    },
      +    "target_url": {
      +      "description": "Your HTTPS endpoint; `null` on every channel except `webhook`.",
      +      "type": "string"
      +    },
      +    "trigger_kind": {
      +      "description": "Event-trigger webhooks only: `event`.",
      +      "type": "string"
      +    },
      +    "universe_id": {
      +      "description": "Universe the trigger is scoped to, or `null` for the whole market.",
      +      "type": "string"
      +    },
      +    "updated_at": {
      +      "description": "Last modification timestamp.",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "id",
      +    "name",
      +    "q",
      +    "rule_id",
      +    "fields",
      +    "order",
      +    "dir",
      +    "universe_id",
      +    "cadence",
      +    "channel",
      +    "target_url",
      +    "delivery",
      +    "status",
      +    "source",
      +    "subscription_origin",
      +    "last_predicate_value",
      +    "created_at",
      +    "updated_at",
      +    "last_fired",
      +    "last_match_set",
      +    "next_eval_at",
      +    "last_evaluated_at"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well by disclosing partial-update semantics, immutability of trigger/channel, and the 400 on unknown fields. It could add more about auth or side effects, but the key behavioral traps are explicitly surfaced.

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?

Three concise sentences with no filler. The main usage instruction is front-loaded, followed by the most important constraint and error 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 description covers the main gotchas (immutability, partial update, unknown-field rejection) and the richly described schema plus output schema fill in parameter and return details. A few edge cases like idempotency or permission requirements are not mentioned, but nothing essential is missing for correct invocation.

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 description does not need to explain individual parameters. The description adds general context about partial updates and unknown fields, but no specific parameter meaning beyond what the schema already provides.

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 opens with a specific action and resource ('Edit a webhook in place'), and immediately defines the update scope ('send only the fields you want to change'). It also distinguishes itself from sibling tools by calling out immutable trigger/channel and directing to delete/re-create instead.

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 explicit usage guidance: partial updates are expected, and users are directed to delete and re-create when changing immutable trigger or channel fields. It does not explicitly mention alternatives like enable_webhook, but the guidance it provides is clear and actionable for the main decision.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.