Skip to main content
Glama

Delete a webhook

autoshort_delete_webhook
DestructiveIdempotent

Deletes a webhook to stop all future deliveries immediately, helping remove unwanted or obsolete endpoints from receiving event notifications.

Instructions

Delete a webhook; deliveries to it stop immediately. Free.

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": {
      "webhookId": "<webhookId>"
    },
    "name": "autoshort_delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the description's bar is lower. It still adds two facts not in the structured data: that deliveries halt immediately upon deletion and that the call is free (no credit cost). It stops short of stating whether the webhook record or its delivery history is permanently lost.

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?

Three short clauses, front-loaded with the action, then effect, then cost — nothing wasted. The telegraphic 'Free.' fragment is slightly clipped but still reads cleanly as a cost note.

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 delete with no output schema, the essential picture (what it does, immediate effect, no cost) is covered, and the annotations supply the destructiveness and idempotency profile. Only the permanence of the deletion and the source of the webhookId are unaddressed.

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?

There is one required parameter, webhookId, with 0% schema description coverage, so the description needed to carry the load. It does not say where to obtain the ID (e.g., from a webhook listing tool) or what format it takes, leaving the single parameter essentially undocumented beyond its name.

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 names a specific verb and resource ("Delete a webhook") in the very first words, so the agent knows exactly what the tool does. It does not explicitly mention the create_webhook sibling or any other alternative, but the operation is unambiguous on its own.

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?

Usage is implied rather than stated: 'deliveries to it stop immediately' signals the consequence of removing a webhook, which is the situation in which one would call it. There is no explicit when-to-use/when-not-to-use framing, no prerequisite (e.g., needing an existing webhookId), and no named alternative.

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