Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Delete webhook

delete_webhook
DestructiveIdempotent

Permanently remove a webhook from a pod to stop its event delivery. Deletion cannot be undone, so verify pod_id and webhook_id first.

Instructions

Delete a webhook. This cannot be undone.

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

Input Schema

NameRequiredDescriptionDefault
pod_idYesA pod id the key can reach. The server rejects any id outside this key's scope.
webhook_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is largely covered. The description's "This cannot be undone" reinforces permanence but is close to redundant with destructiveHint, and it says nothing about permission requirements, side effects on in-flight deliveries, or error behavior for out-of-scope pod ids.

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?

Two short sentences, front-loaded with the action and immediately followed by the consequence. Nothing extraneous; every word earns its place.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter delete with rich annotations and no output schema, the description is minimally sufficient to call the tool safely. It falls short on the undocumented webhook_id and on what a failed or out-of-scope deletion looks like.

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 coverage is only 50%: pod_id has a scoping note but webhook_id has no description at all, and the description adds no parameter meaning whatsoever. With a documented gap in the schema, the description should have compensated and does not.

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+resource ("Delete a webhook") that maps cleanly onto the resource named in the tool name and distinguishes it from create_webhook/get_webhook/update_webhook siblings. It does not explicitly differentiate itself from those siblings, but the verb+resource pairing leaves little ambiguity.

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 alternatives such as update_webhook (disable instead) or test_webhook, and no mention of prerequisites or what happens to the webhook's delivery history. The only usage-adjacent statement is the irreversibility warning.

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