Skip to main content
Glama

Webhooks Destroy

webhooks_destroy

Delete a webhook from an organisation by specifying the organisation and webhook IDs, removing it from the webhook configuration.

Instructions

Delete a webhook. DELETE /organisations/{organisationId}/webhooks/{webhookId}

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": {
      "organisation_id": "<organisation_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "webhooks_destroy"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Delete' implies a mutation, but the definition never states that the operation is irreversible, what happens to existing deliveries or subscriptions tied to the webhook, or whether any confirmation or elevated scope is required.

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?

Two short sentences with the action front-loaded and no filler. It is efficient, though the endpoint restatement is thin value relative to the missing guidance.

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 a destructive, irreversible operation with no annotations, no output schema, and 0% parameter documentation, the definition is too sparse. An agent still lacks consequence disclosure and permission context needed to invoke it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and largely does not. The URL template does implicitly reveal that both parameters are path identifiers rather than body fields, which is marginal added meaning, but no format, ID-shape, or validity detail is given.

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 states a specific verb and resource ('Delete a webhook'), which clearly distinguishes it from webhooks_create, webhooks_index and webhooks_show by action. It does not explicitly name or contrast with those siblings, so it falls short of the top band.

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 when-to-use guidance, no mention of prerequisites such as ownership or permissions, and no warning about when deletion should be avoided. The agent must infer the entire usage context from the one-word verb.

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