Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete webhook

delete_webhook
Destructive

Permanently removes a webhook endpoint by ID, stopping event notifications for a decommissioned integration or outdated endpoint.

Instructions

Delete a webhook endpoint permanently.

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": {
      "id": "<id>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv0.73.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description's one addition, 'permanently', reinforces irreversibility but does not disclose what else is affected (e.g., pending deliveries or delivery history), whether confirmation is expected, or what errors occur for an unknown id.

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?

One sentence, front-loaded with the verb and resource, with zero filler. The word 'permanently' is the only qualifier and it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with no output schema and an undocumented `id`, the definition is too thin. It omits whether deletion is recoverable, whether related delivery records persist, and what success looks like, all of which an agent needs before invoking an irreversible delete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

This is a single-parameter tool, and the description correctly frames it as affecting one specific webhook endpoint. The schema only documents `id` as a string with minLength 1, which is sufficient for this contract. The description does not add id format or sourcing guidance, but for one plain string parameter the cost is minor.

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 pairs a specific verb (Delete) with a specific resource (a webhook endpoint), so an agent immediately knows the operation. It does not, however, distinguish this from sibling webhook tools such as update_webhook or rotate_webhook_secret, so the differentiation is left to the name alone.

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 when-to-use guidance, no prerequisites, and no mention of when an agent should prefer update_webhook or handle webhook cleanup another way. The only implicit signal is 'permanently', which hints at caution but states nothing actionable.

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

Deploy Server

Other Tools