Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_delete_webhook_subscription

DestructiveIdempotent

Permanently deletes a webhook subscription so no further events are delivered to its URL. Use it to remove a subscription entirely; set active to false instead to stop deliveries reversibly.

Instructions

Permanently deletes a webhook subscription. No further events are delivered to its URL. To stop deliveries reversibly, set active to false instead.

BeeL API endpoint: DELETE /v1/accounts/{account_id}/webhooks/{webhook_id} (reference: https://docs.beel.es)

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": {
      "account_id": "<account_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "beel_delete_webhook_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesYour own account, or an account you provisioned. It — not the credential, and not the `BeeL-Active-Company` header — decides which account the operation acts on. An account you do not reach answers `403`, and so does an account that does not exist, so the existence of somebody else's account is never disclosed.
webhook_idYesSubscription of the account in the path. A subscription of another account answers `404`, the same as one that does not exist: under the account resolved from `{account_id}` it simply is not there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.3.1

TDQS

A4.5/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 covered. The description still earns credit for spelling out what is actually destroyed — the subscription itself and all future event delivery — plus the reversible alternative. It stops short of saying whether delivery history or logs survive the deletion, which is the one behavior an agent might still wonder about.

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, front-loaded with the destructive consequence, then the reversible alternative, then the API reference. Every sentence carries distinct information and nothing is repeated from the annotations or schema.

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

Completeness5/5

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

For a two-parameter destructive tool with full annotation coverage and no output schema, the description supplies everything needed to call it correctly: the effect, the irreversibility, the alternative, and the endpoint. The only unaddressed detail is post-deletion retention of delivery records, which is not essential to invoking the call.

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?

Schema description coverage is 100% and both parameters are richly documented in the schema, including the 403/404 disclosure semantics for cross-account access. The description adds only the endpoint template, which maps the parameters to path segments but adds no meaning beyond what the schema already states, so the baseline 3 applies.

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?

The description opens with a specific verb and resource ("Permanently deletes a webhook subscription") and immediately states the operational consequence ("No further events are delivered to its URL"). It also distinguishes itself from the reversible path by naming the `active` = `false` alternative, so an agent can tell it apart from `beel_patch_webhook_subscription` without opening either 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?

It gives an explicit when-not-to-use rule: to stop deliveries reversibly, set `active` to `false` instead. That is a direct routing instruction to the sibling patch tool, and the endpoint line confirms the underlying resource path.

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

Deploy Server

Other Tools