Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_create_webhook_subscription

Idempotent

Registers an HTTPS endpoint to receive signed webhook notifications for selected invoice and account event types, returning the signing secret and an optional test delivery.

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 with 400 WEBHOOK_ACTIVE_SUBSCRIPTION_LIMIT_REACHED. Registering the same URL twice creates two subscriptions, and the endpoint then receives each event twice.

BeeL API endpoint: POST /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>",
      "body": "<body>"
    },
    "name": "beel_create_webhook_subscription"
  }
}

Input 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. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / body / type
      Added value: +"object"
  2. Changed2 schema fields changedv0.9.0
    • 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 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.pdf.generated` — The PDF of an invoice was (re)rendered, so any copy you cached\n  is stale; fetch it again from the PDF endpoint\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- `invoice.schedule_failed` — A scheduled invoice could not be issued on its date and BeeL.\n  gave up retrying; it stays in drafts and can be issued by hand once the cause is fixed\n- `verifactu.status.updated` — VeriFactu public 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"
    • changedInput schema / $defs / WebhookEventTypeEnum / enum
      Previous value: -[
      -  "invoice.issued",
      -  "invoice.email.sent",
      -  "invoice.voided",
      -  "recurring_invoice.paused",
      -  "verifactu.status.updated",
      -  "account.claimed",
      -  "company.created",
      -  "representation.signed"
      -]New value: +[
      +  "invoice.issued",
      +  "invoice.email.sent",
      +  "invoice.pdf.generated",
      +  "invoice.voided",
      +  "recurring_invoice.paused",
      +  "invoice.schedule_failed",
      +  "verifactu.status.updated",
      +  "account.claimed",
      +  "company.created",
      +  "representation.signed"
      +]
  3. 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
  4. First observedv0.3.1

TDQS

A3.9/5.0
Behavior5/5

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

The description adds substantial behavior beyond annotations: the `secret` is returned only once and used to sign deliveries via `BeeL-Signature`; `test_delivery` is a one-off best-effort signed delivery that can be null; the account relationship options are explained; and hard limits plus duplicate-subscription side effects are disclosed. This gives an agent rich operational context.

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?

The description is front-loaded with the core action, then uses labeled bullets for key facts. Every bullet carries useful information (secret one-time return, test delivery semantics, account relationship, limits). It is slightly dense but well structured and free of obvious filler.

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?

For a create operation with no output schema, the description compensates by explaining key response fields (`secret`, `test_delivery`), side effects, and limits. It does not describe the full response shape or authentication requirements, but those gaps are minor relative to the complexity of the tool.

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 moderate (67%), and the schema already documents all three parameters in detail, including `account_id`, `idempotency_key`, and the nested `body` fields. The description reinforces `events` and `account_relationship`, but adds little parameter-level meaning beyond the schema and does not mention `idempotency_key` directly.

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: 'Registers an HTTPS endpoint to receive notifications for the event types listed in `events`.' It is clear what the tool does and implicitly create-specific, but it does not explicitly name or differentiate from siblings like `beel_test_webhook_subscription` or `beel_patch_webhook_subscription`.

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: create a webhook subscription with a URL and event types. The description adds caveats (10-subscription limit, duplicate URL behavior, best-effort test delivery) but never says when to use this tool versus alternatives such as testing an existing subscription or updating one. No explicit when-not guidance is provided.

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