Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Delete Webhook

delete_webhook
DestructiveIdempotent

Removes a webhook endpoint and stops all deliveries immediately. Use update_webhook(enabled=false) instead when you only need to pause deliveries.

Instructions

Remove a webhook endpoint. Deliveries stop immediately. Prefer update_webhook(enabled=false) to pause instead.

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": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known. The description still adds real value beyond them by stating that deliveries stop immediately and by steering to a reversible pause path; it does not say whether the webhook config is permanently unrecoverable, which is the main remaining gap.

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, each earning its place: the action, the consequence, and the alternative. The consequence and the alternative are front-loaded rather than buried.

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?

An output schema exists so return values need not be described, and for a one-parameter destructive delete the description covers the effect and the safer alternative. What it lacks is any identification of the webhook_id parameter, which is the one thing an agent must supply.

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 carry the meaning of the single webhook_id parameter — and it says nothing about it (no format, no source such as list_webhooks, no example). The baseline for one parameter is not available here because the schema coverage is effectively zero, and the description does not compensate.

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 and resource ('Remove a webhook endpoint') plus the immediate effect, and names the sibling alternative, so an agent can distinguish it from update_webhook or list_webhooks without opening the schema.

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?

Explicitly routes the agent: use this to remove, but prefer update_webhook(enabled=false) to pause instead. That is a direct when-to-use-vs-alternative rule, not an implied one.

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