Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_delete_webhook

Delete a webhook and its delivery history to remove unused subscription endpoints and prevent further notifications.

Instructions

Deletes a webhook and its delivery history.

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_delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookYesWebhook id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.1
    • removedInput schema / properties / id
      Removed value: -{
      -  "description": "Webhook id (looks like `wh_…`).",
      -  "type": "string"
      -}
    • addedInput schema / properties / webhook
      Added value: +{
      +  "description": "Webhook id.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id"
      -]New value: +[
      +  "webhook"
      +]
  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?

With no annotations supplied, the description carries the full behavioral burden. It does disclose a meaningful side effect beyond the tool name: the webhook's delivery history is destroyed along with it. However, it never states that the operation is irreversible, whether confirmation or elevated permissions are required, or what failure behavior looks like for a destructive mutation.

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 short sentence, front-loaded with the action and including the one non-obvious consequence. No filler or redundant restatement of the tool name.

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 one-parameter delete tool with no output schema and no annotations, the description covers the essentials of what is removed, including the cascading deletion of delivery history. It is still thin on irreversibility and error conditions, which matter most for an unannotated destructive operation.

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 coverage is 100% and the single parameter is documented as "Webhook id." in the schema, so the description adds nothing further about identifier format or source. Baseline 3 applies when the schema already does the work.

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 gives a specific verb (Deletes) and resource (a webhook), so an agent can immediately tell it apart from get/list/update/enable webhook siblings. It stops short of explicitly differentiating deletion from alternatives like update_webhook or disable-style operations, but the resource-level match is unambiguous.

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?

There is no guidance on when to delete versus update or disable a webhook, no prerequisite that the webhook must exist, and no indication of what happens on a webhook id that is already gone. The agent must infer all usage conditions from the name alone.

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