Skip to main content
Glama

delete_webhook

Destructive

Delete a webhook; events stop being sent to that URL. (confirm-gated: previews until confirm: true)

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
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 known; the description adds real value on top by stating the downstream effect (event delivery stops) and the two-phase confirm-gated execution. It stops short of saying whether the webhook can be restored or what the preview response contains, which keeps it below a 5.

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?

Two short clauses with the consequence front-loaded and the execution gate in parentheses; no filler, and the most decision-relevant information leads.

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 destructive mutation with no output schema, the description covers what is destroyed and the confirmation mechanism, which is the core need. It omits whether deletion is permanent, whether delivery history is retained, and what the preview reveals, so it is adequate but not complete for a destructive tool.

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 50%: 'confirm' is already fully documented in the schema, and the description's 'previews until confirm: true' repeats it rather than extending it. The undocumented 'id' parameter is left uncharacterized (webhook ID format, where to obtain it) though its meaning is largely self-evident, so the description neither compensates for nor deepens the schema.

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?

States a specific verb and resource ('Delete a webhook') and immediately names the observable consequence ('events stop being sent to that URL'), which is exactly what distinguishes deletion from the deactivation offered by set_webhook_active. An agent can classify the operation without opening the schema.

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

Usage Guidelines3/5

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

The description conveys the confirm-gate workflow, which is genuine usage guidance for invoking it correctly. However, it gives no explicit guidance on when to delete versus when to deactivate via set_webhook_active, and no prerequisites or warnings about irreversibility, leaving the delete-vs-disable decision to inference.

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.