Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_get_webhook_subscription

Read-onlyIdempotent

Fetch a webhook subscription by account ID and webhook ID to review its configuration without exposing the signing secret.

Instructions

Returns a single webhook subscription. The signing secret is never included.

BeeL API endpoint: GET /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_get_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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact, that the signing secret is never in the response, plus the underlying endpoint; it doesn't cover error behavior or response shape (the 404/403 semantics live in the schema).

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?

Front-loaded with the core action, followed by one useful caveat, then endpoint and doc reference. Efficient with no filler, though the endpoint/reference line is somewhat redundant for an agent that already has the tool name.

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?

The tool is simple with full schema coverage and no output schema. The description doesn't describe what fields a subscription returns (url, events, status, etc.), so an agent lacks a picture of the response payload; annotations cover the safety side, leaving this a moderate but real gap.

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%, so both account_id and webhook_id are fully documented in the schema, including cross-account 403/404 behavior. The description adds nothing about parameters beyond what the schema already provides, so baseline 3 applies.

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 ('Returns a single webhook subscription'), and 'single' implicitly separates it from beel_list_webhook_subscriptions. It doesn't name the sibling explicitly, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'single' suggests fetching one known subscription rather than listing, but there is no explicit when-to-use statement, no alternative named, and no note about when to prefer the list tool.

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