Skip to main content
Glama

delete_webhook

Delete a webhook endpoint by uuid, so it stops receiving events. Use it to remove an endpoint for good; to stop deliveries temporarily use update_webhook with status paused. Repeating the call on a deleted endpoint is safe. Requires the webhooks:delete scope.

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_uuid": "<webhook_uuid>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_uuidYesPublic UUID of the webhook endpoint, as returned by create_webhook or list_webhooks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses idempotency ('Repeating the call on a deleted endpoint is safe') and the required 'webhooks:delete' scope, both non-obvious behaviors. It stops short of saying whether queued deliveries are dropped or what the response looks like, so not quite 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?

Three short sentences, front-loaded with the action and its effect, then the alternative, then the safety/scope notes. Every sentence earns its place with no filler.

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

Completeness5/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 no annotations and no output schema, the description covers effect, permanence, the softer alternative, idempotency and required scope. Nothing an agent needs in order to invoke it correctly is missing.

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?

One parameter with 100% schema description coverage, and the schema already explains it is the public UUID returned by create_webhook or list_webhooks. The description only echoes 'by uuid', adding no format or sourcing detail beyond the schema, so the baseline 3 applies.

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, resource and identifier ('Delete a webhook endpoint by uuid') plus the effect ('stops receiving events'). It also implicitly separates itself from get_webhook/list_webhooks and update_webhook, so an agent can pick it without consulting sibling schemas.

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

Usage Guidelines5/5

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

Explicit routing: use this for permanent removal, use update_webhook with status paused for temporary stop. That names the alternative and the condition that selects it, which is exactly the guidance an agent needs.

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