Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

beel_patch_webhook_subscription

Update an existing webhook subscription's URL, subscribed events, active status, or account relationship while preserving unmentioned settings.

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.

  • Signing secret: not touched here. Rotate it with POST /v1/accounts/{account_id}/webhooks/{webhook_id}/secret.

Endpoint: PATCH /v1/accounts/{account_id}/webhooks/{webhook_id}

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.
webhook_idYesSubscription 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. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv0.5.0
    • 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
  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?

It discloses non-obvious mutation semantics: events replaces the whole list rather than appending, active=false preserves delivery history, and a subscription deactivated by beel needs a successful test before reactivation. These behaviors go well beyond the annotations and materially affect how an agent should invoke the tool.

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 description is front-loaded with the core partial-update behavior and uses compact bullet points. Every sentence carries operational value, and the endpoint line gives useful orientation without bloating the text.

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 mutation tool with no output schema, the description covers the most important pitfalls: replacement semantics, deactivation behavior, reactivation requirements, and the signing-secret exclusion. It does not describe the response shape or what happens with an empty body, but those are relatively minor gaps given the annotations and schema richness.

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 schema already documents the fields well, so the baseline is valid. The description adds crucial semantics for events and active that the schema's one-line descriptions do not convey, and it clarifies that the signing secret is not part of the patch body. The url and account_relationship parameters add less new meaning, but they are already well covered by their schema descriptions.

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 description states a precise operation: PATCH-updating a webhook subscription by modifying only the fields present in the body. It names the affected fields and explicitly differentiates the tool from create/delete/replace operations with the 'leaves the rest untouched' clause.

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 clearly excludes the signing secret and references a dedicated rotate endpoint, which gives an explicit when-not and alternative. It does not explicitly contrast with create_webhook_subscription or delete_webhook_subscription, but the PATCH verb and 'Updates' make the main usage context evident.

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