Skip to main content
Glama

Delete a webhook

delete_webhook
DestructiveIdempotent

Delete one of the user's webhooks, when the user asks: Werify stops sending to its address at once, and the deliveries still waiting are dropped. What the address already received stays there.

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_id": "<webhook_id>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_idYesFrom list_webhooks.

Output Schema

NameRequiredDescriptionDefault
hostNo
deletedNo
webhook_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description earns credit for adding concrete effects beyond that: sending stops immediately, queued deliveries are dropped, and already-received deliveries are unaffected. It still does not say whether deletion is reversible or whether any auth/permission is required, so it falls short of 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.

Conciseness4/5

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

One front-loaded sentence that puts the verb and resource first and then explains consequences; nothing is padded. Minor deductions for the awkward mid-sentence 'when the user asks:' colon construction and a typo ('Werify'), which slightly impede scanning.

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?

For a single-parameter destructive tool with an output schema and rich annotations, the description supplies the missing piece: what actually happens to deliveries at deletion time. Recoverability and permission requirements remain unstated, which keeps it short of complete.

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 with a source ('From list_webhooks'), so the baseline of 3 applies. The description adds no further meaning about the identifier's format or how to obtain it, leaving the schema to carry the load.

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?

States a specific verb and resource ('Delete one of the user's webhooks') plus the scope of ownership (the user's), so the agent knows exactly which object is affected. It does not explicitly contrast with create_webhook or list_webhooks, but the name plus the ownership qualifier makes the distinction obvious.

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 phrase 'when the user asks' gives a weak trigger condition for invocation, which is more than nothing. However, there is no guidance on prerequisites, on checking the webhook exists first, or on when to use this rather than disabling or recreating a webhook; the pointer to list_webhooks appears only in the schema, not the description.

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.

Resources