BeeL MCP server

Official

Overview Schema Source Related Servers Discussions Admin

beel_patch_webhook_subscription

Destructive

Modify an existing webhook subscription's endpoint URL, event list, active flag, or account scope in place, leaving untouched fields and the signing secret unchanged.

Instructions

Updates the fields present in the body — url, events, active, account_relationship — and leaves the rest untouched.

events: replaces the whole list, it does not add to it, so an event left out of it stops being delivered.
active: setting it to false stops deliveries without discarding the delivery history. A subscription we turned off ourselves (deactivated_by: beel) needs a successful test delivery before it can be turned back on. Turning a subscription back on counts towards the limit of 10 active subscriptions, and is rejected with 400 WEBHOOK_ACTIVE_SUBSCRIPTION_LIMIT_REACHED when ten are already active.
Signing secret: not touched here. Rotate it with POST /v1/accounts/{account_id}/webhooks/{webhook_id}/secret.

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

Input Schema

Name	Required	Description
`body`	Yes
`account_id`	Yes	Your 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_id`	Yes	Subscription 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.

Changed1 schema field changedv0.10.0Nov 5, 2026
- addedInput schema / properties / body / type
```
Added value: +"object"
```

Changed2 schema fields changedv0.9.0Oct 1, 2026

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"
+]

Changed7 schema fields changedv0.5.0Aug 30, 2026

addedInput schema / $defs / UpdateWebhookSubscriptionRequest / additionalProperties
```
Added value: +false
```
removedInput schema / $defs / UpdateWebhookSubscriptionRequest / properties / account_relationship / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/WebhookAccountRelationship"
-  }
-]
```

addedInput schema / $defs / UpdateWebhookSubscriptionRequest / properties / account_relationship / anyOf

Added value: +[
+  {
+    "allOf": [
+      {
+        "$ref": "#/$defs/WebhookAccountRelationship"
+      }
+    ],
+    "description": "New set of accounts this subscription receives events from. Same field name and values as the `account_relationship` carried by every event envelope.\n"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / $defs / UpdateWebhookSubscriptionRequest / properties / account_relationship / description

Removed value: -"New set of accounts this subscription receives events from. Same field name and values as the `account_relationship` carried by every event envelope.\n"

removedInput schema / $defs / UpdateWebhookSubscriptionRequest / 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
```

First observedv0.3.1Aug 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false): it warns that `events` replaces the whole list so omitted events stop being delivered, that `active: false` preserves delivery history, that self-deactivated subscriptions require a test delivery to re-enable, and it surfaces the exact 400 WEBHOOK_ACTIVE_SUBSCRIPTION_LIMIT_REACHED failure. These are real, non-inferable behavioral consequences an agent needs before mutating.

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-loads the core contract in the first sentence, then uses bold-labeled bullets keyed to the affected fields for scannability. The endpoint/reference footer is boilerplate and the signing-secret bullet is somewhat tangential, but nothing else is padding.

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 destructive mutation with no output schema, the description covers the risky semantics, error condition, and cross-endpoint boundary, which is most of what an agent needs. It does not say what the response returns or whether changing `url` requires re-verification of the endpoint, which are the remaining gaps.

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

Parameters5/5

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

Schema coverage is only 67%, but the description compensates strongly: it clarifies that `events` is a full replacement rather than an append, spells out the state machine behind `active`, and explicitly excludes the signing secret from this operation. This adds meaning that the schema's terse "New list of event types to subscribe to" does not convey.

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?

States a specific verb and resource ("Updates the fields present in the body … and leaves the rest untouched") and enumerates the exact mutable fields, so the PATCH/partial-update semantics are unmistakable. It also pre-empts confusion with the secret-rotation operation by naming that separate endpoint, which is the closest sibling ambiguity here.

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?

Gives concrete usage context: modifying an existing subscription's url/events/active/account_relationship, plus the reactivation path (needs a successful test delivery, counts toward the 10-active limit). It stops short of explicitly routing the agent to siblings like create/delete/test webhook subscription, but the conditions for use are clear.

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

Deploy Server