Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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.

  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.6/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true), the description reveals unique behavioral facts: the secret is returned only once, deliveries are signed with BeeL-Signature, test_delivery is best-effort, an account is limited to 10 active subscriptions, and registering the same URL twice duplicates the webhook. No statement contradicts the annotations.

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?

Bulleted format front-loads the most critical operational facts after a one-sentence summary. Every bullet carries necessary information; it is longer than average but justified by the webhook-specific pitfalls it documents.

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?

The lack of an output schema makes the description the only source for understanding the response. It covers the two most unusual parts (`secret` and `test_delivery`), but it stops short of describing the full subscription object or error/status code behavior, so a small completeness gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaningful context for the `events` and `account_relationship` parameters (ownership semantics, test delivery, limits), while the input schema already documents `url`, `account_id`, and `idempotency_key`. With 67% schema coverage, the description partially compensates without fully covering every parameter.

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?

Opens with a specific verb and resource: 'Registers an HTTPS endpoint to receive notifications for the event types listed in `events`.' This clearly differentiates it from the sibling test/patch/rotate webhook tools and matches the tool's name and title.

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

Usage Guidelines4/5

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

The description does not explicitly name sibling alternatives or state exclusions, but it establishes clear context: creation happens via POST, the subscription is active even if the test delivery fails, and duplicate URLs create two deliveries. This is enough for an agent to recognize the create path, though it could have pointed to beel_test_webhook_subscription for probing an endpoint afterward.

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