Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_list_webhook_subscriptions

Read-onlyIdempotent

Lists all active and inactive webhook subscriptions for a specified account, with pagination, so you can audit webhook registrations without exposing signing secrets.

Instructions

Returns the webhook subscriptions of the account in the path, active and inactive alike. Every member of the account sees the same list: who registered a subscription is authorship, not visibility. The signing secrets are never included.

BeeL API endpoint: GET /v1/accounts/{account_id}/webhooks (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>"
    },
    "name": "beel_list_webhook_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. The response echoes it back as `pagination.current_page`.
limitNoHow many items to return per page. The response echoes it back as `pagination.items_per_page`.
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.

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: all members of the account see an identical list regardless of who registered a subscription, and signing secrets are never included in the payload. That is genuine disclosure about visibility and data redaction that no annotation carries. It stops short of describing ordering or response envelope details.

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 statement, followed by two short clauses that each carry distinct information (visibility model, secret redaction). The trailing endpoint/docs line is useful for traceability but is somewhat boilerplate; otherwise there is no waste.

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?

With no output schema, the description could do more to sketch the return shape, but the schema's page/limit descriptions already reveal the pagination envelope and annotations cover the safety profile. Combined, an agent has enough to call it correctly; only ordering/default-sort behavior is unstated.

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 the account_id, page and limit descriptions are already exhaustive (including 403 masking behavior and pagination echo fields). The description only restates 'the account in the path' and adds nothing about parameter meaning, so 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?

Specific verb+resource: returns webhook subscriptions for an account, and it explicitly states the scope ('active and inactive alike'), which an agent could not infer from the name alone. The resource is clearly distinct from sibling beel_get_webhook_subscription (single) and beel_list_webhook_deliveries (delivery attempts).

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 implied by the list semantics and the stated scope, but the description never names an alternative (e.g. beel_get_webhook_subscription for one subscription, or the deliveries sibling) or states a when-not condition. There is also no mention of whether pagination must be walked to see everything.

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