Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

beel_create_webhook_subscription

Idempotent

Register an HTTPS endpoint to receive signed webhook notifications for selected invoice, VeriFactu, and account events. Includes a test delivery to verify your endpoint responds.

Instructions

Registers an HTTPS endpoint to receive notifications for the event types listed in events.

  • secret: returned only in this response and never again. Store it before discarding the body; deliveries are signed with it and carry the signature in the BeeL-Signature header.

  • test_delivery: a one-off signed delivery sent to your URL as part of creating the subscription, so you learn whether your endpoint answers without a second call. It is best effort: the subscription exists and is active whatever it says, and the field is null when the test could not be run at all.

  • account_relationship: which accounts the subscription receives events from — own (the default), managed, or all.

  • Limits: an account holds at most 10 active subscriptions; creating an eleventh is rejected. Registering the same URL twice creates two subscriptions, and the endpoint then receives each event twice.

Endpoint: POST /v1/accounts/{account_id}/webhooks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
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.
idempotency_keyNoOptional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.5.0
    • addedInput schema / $defs / CreateWebhookSubscriptionRequest / additionalProperties
      Added value: +false
    • removedInput schema / $defs / CreateWebhookSubscriptionRequest / properties / events / example
      Removed value: -[
-  "invoice.issued",
-  "verifactu.status.updated"
-]
    • removedInput schema / $defs / CreateWebhookSubscriptionRequest / properties / url / example
      Removed value: -"https://yourapp.com/webhooks/beel"
    • changedInput schema / $defs / WebhookEventTypeEnum / description
      Previous value: -"Available webhook event types:\n- `invoice.issued` — Invoice issued and finalized\n- `invoice.email.sent` — Invoice sent by email\n- `invoice.voided` — Invoice voided\n- `recurring_invoice.paused` — A schedule stopped generating on its own (downgrade or a\n  permanent generation failure); the invoice it was going to issue will not arrive\n- `verifactu.status.updated` — VeriFactu status changed (see `VeriFactuSubmissionStatus`)\n- `account.claimed` — A provisioned account was claimed by its holder\n- `company.created` — A NIF (company) was created inside a provisioned account\n- `representation.signed` — Fiscal representation signed for a NIF (production invoicing enabled)\n\nThe `account.*` events are delivered only to the **provisioner** that created the\naccount; a subscription on any other account never receives them.\n"New value: +"Available webhook event types:\n- `invoice.issued` — Invoice issued and finalized\n- `invoice.email.sent` — Invoice sent by email\n- `invoice.voided` — Invoice voided\n- `recurring_invoice.paused` — A schedule stopped generating on its own (downgrade or a\n  permanent generation failure); the invoice it was going to issue will not arrive\n- `verifactu.status.updated` — VeriFactu status changed (see `VeriFactuSubmissionStatus`)\n- `account.claimed` — A provisioned account was claimed by its holder\n- `company.created` — A company was created inside a provisioned account\n- `representation.signed` — Fiscal representation signed for a NIF (production invoicing enabled)\n\nThe `account.*` events are delivered only to the **provisioner** that created the\naccount; a subscription on any other account never receives them.\n"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.3.1

TDQS

A4.3/5.0
Behavior5/5

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

The description discloses several non-obvious behaviors beyond the annotations: the secret is returned only once and must be stored, test_delivery is best-effort and null when it cannot run, an account is limited to 10 active subscriptions, and registering the same URL twice creates duplicate subscriptions. These are precisely the kind of side effects an agent needs to know and which annotations alone do not convey. The duplicate-URL statement is not a direct contradiction of idempotentHint because it refers to distinct registrations rather than an identical idempotent request.

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?

The intro is front-loaded and the four bulits each carry an essential operational fact rather than fluff. There is no filler; even the endpoint line adds useful routing context. The length is justified by the number of side effects and response caveats.

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 create tool without an output schema, the description explains the two critical response fields (secret and test_delivery), the operational limits, and the duplicate-delivery consequence. Combined with the schema's idempotency-key and enum documentation, an agent has the necessary information to invoke the tool and interpret its response correctly.

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?

The schema already provides rich descriptions for account_id, idempotency_key, url, events, and account_relationship, and the description mostly restates account_relationship's own/managed/all behavior without adding new input semantics. The secret and test_delivery bullets describe response fields, not parameters, so they don't improve parameter understanding. With 67% schema coverage and detailed nested schemas, baseline 3 is appropriate.

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 opening sentence states a specific action and resource: 'Registers an HTTPS endpoint to receive notifications for the event types listed in events.' This clearly identifies the tool as webhook-subscription creation and distinguishes it from sibling webhook tools such as get, list, patch, test, and delete. The endpoint line reinforces the operation without ambiguity.

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?

The description implies the tool is for creating webhook subscriptions and even describes the built-in test delivery, but it never explicitly says when to choose this over alternatives like beel_test_webhook_subscription or beel_patch_webhook_subscription. There is no when-not-to-use guidance or explicit comparison to siblings, so usage context is available but mostly implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/beel-es/beel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server