Skip to main content
Glama

webhook_delete

Delete an outgoing 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": {
      "webhook_id": "<webhook_id>"
    },
    "name": "webhook_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 bears the full burden. "Delete" signals a destructive mutation, but nothing states whether removal is permanent, whether it requires ownership or admin rights, or whether in-flight deliveries fail or are dropped. For an irreversible operation with zero annotation coverage, that is a meaningful gap.

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 short sentence, front-loaded with the verb and resource, with no filler or redundancy. Its brevity is not the problem; the missing information belongs to the other dimensions.

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 single-parameter tool with no annotations and no output schema, the definition should at minimum state permanence, required permissions, and where the webhook_id comes from. None of that is present, so the agent can identify the tool but cannot call it confidently.

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?

The single parameter webhook_id has 0% schema description coverage and the description adds no meaning — it never says whether the value is an opaque ID or a URL, or how the caller obtains it (e.g., from webhook_list). With only one parameter this is recoverable, but the description does not compensate for the coverage gap.

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?

"Delete an outgoing webhook endpoint" gives a specific verb (delete) plus a specific resource (outgoing webhook endpoint), which clearly separates it from webhook_create and webhook_list among the siblings. It stops short of stating scope or side effects, but the core purpose is unambiguous.

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 use this versus webhook_list or webhook_create, no prerequisites, and no note about what happens to events already queued for the endpoint. The agent must infer that this is the teardown path for a webhook it previously created.

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