Skip to main content
Glama

Delete webhook

webhook_delete
Destructive

Deletes a webhook endpoint.

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": "webhook_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWebhook endpoint ID from webhook_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Webhook endpoint ID from webhook_list."
  2. First observed

TDQS

C2.3/5.0
Behavior2/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 without the description. The description adds nothing beyond that: it doesn't say the deletion is irreversible, whether pending deliveries or delivery history are removed, or whether the endpoint must be disabled first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, but it is sparse to the point of being uninformative rather than genuinely concise. There is no structure because there is only one clause.

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 an irreversible destructive operation with no output schema, an agent needs to know the consequences and side effects, none of which are stated. The parameter is fully documented in the schema, but the behavioral picture is incomplete.

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% and the id parameter is documented as coming from webhook_list, so the schema carries the meaning. The description contributes no additional parameter context, which is the baseline expectation at full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence "Deletes a webhook endpoint" restates the tool name (webhook_delete) and title (Delete webhook) almost verbatim, so it adds no distinguishing information. It never clarifies how this differs from siblings like org_webhook_delete or webhook_enable.

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 call this versus disabling a webhook (webhook_enable), listing it (webhook_list), or using the org-scoped variant. No prerequisites, no warnings about confirming before a destructive call.

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.