BeeL MCP server

Official

Overview Schema Source Related Servers Discussions Admin

beel_update_invoice_customization

Idempotent

Update a company's invoice settings: PDF template, accent color, invoice language, and email language. Changes apply only to invoices issued afterward.

Instructions

Updates how the invoices of a company are rendered and delivered: PDF template, accent colour, invoice language and email language. Only the properties present in the request body are modified, and the logo is managed through the logo sub-resource.

The change applies to invoices rendered after it and does not alter already issued documents.

Endpoint: PUT /v1/companies/{company_id}/invoice-customization

Input Schema

TableJSON Schema

Name	Required	Description	Default
`body`	Yes
`company_id`	Yes	Unique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.0Oct 1, 2026

changedInput schema / $defs / Language / description

Previous value: -"Supported languages"New value: +"Supported languages: `es` Spanish, `en` English, `ca` Catalan.\n"

Changed11 schema fields changedv0.5.0Aug 30, 2026

removedInput schema / $defs / InvoiceTemplateType / example
```
Removed value: -"MODERN_TABLE"
```
removedInput schema / $defs / Language / example
```
Removed value: -"es"
```
addedInput schema / $defs / UpdateInvoiceCustomizationRequest / additionalProperties
```
Added value: +false
```

changedInput schema / $defs / UpdateInvoiceCustomizationRequest / properties / email_language / allOf

Previous value: -[
-  {
-    "$ref": "#/$defs/Language"
-  },
-  {
-    "description": "Language used for the emails that deliver the invoice."
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/Language"
+  },
+  {
+    "anyOf": [
+      {
+        "description": "Language used for the emails that deliver the invoice."
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+]

removedInput schema / $defs / UpdateInvoiceCustomizationRequest / properties / invoice_accent_color / example
```
Removed value: -"#fc481d"
```

changedInput schema / $defs / UpdateInvoiceCustomizationRequest / properties / invoice_language / allOf

Previous value: -[
-  {
-    "$ref": "#/$defs/Language"
-  },
-  {
-    "description": "Language used to render the invoice PDF."
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/Language"
+  },
+  {
+    "anyOf": [
+      {
+        "description": "Language used to render the invoice PDF."
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+]

removedInput schema / $defs / UpdateInvoiceCustomizationRequest / properties / invoice_template_type / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/InvoiceTemplateType"
-  }
-]
```

addedInput schema / $defs / UpdateInvoiceCustomizationRequest / properties / invoice_template_type / anyOf

Added value: +[
+  {
+    "allOf": [
+      {
+        "$ref": "#/$defs/InvoiceTemplateType"
+      }
+    ],
+    "description": "Template used to render the invoice PDF."
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / $defs / UpdateInvoiceCustomizationRequest / properties / invoice_template_type / description
```
Removed value: -"Template used to render the invoice PDF."
```
addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / company_id / description

Previous value: -"NIF (company) the operation acts on. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A NIF you do not reach answers `403`, and so does a NIF that does not exist, so the existence of a NIF in another account is never disclosed."New value: +"Unique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed."

First observedv0.3.1Aug 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: only present properties are modified, the change applies only to invoices rendered afterwards, and already-issued documents are untouched — exactly the kind of blast-radius detail an agent needs before mutating billing configuration.

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?

Three sentences plus an endpoint line, front-loaded with the resource and its facets, then partial-update semantics, then scope of effect. No filler; the endpoint line is mildly redundant with the tool name but useful for an API-shaped tool.

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 partial-update PUT with no output schema, the description covers what changes, that the update is partial, what it does not affect, and the logo exception. Missing only peripheral details such as auth/permission requirements and the response shape, which are not critical to selecting or invoking the tool.

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 enumerates the four updatable body fields and reiterates the partial-update rule, which the schema also states. The company_id parameter carries a very rich schema description (UUID, not NIF, 403 on unknown company, header not used), so the description does not need to repeat it. It adds marginal meaning, not redundant noise.

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 (Updates) and the exact resource (how a company's invoices are rendered and delivered), then enumerates the four mutable facets: PDF template, accent colour, invoice language, email language. It also explicitly carves the logo out toward its own sub-resource, so an agent can distinguish this from beel_delete_company_logo or beel_get_invoice_customization without opening a schema.

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?

It routes the logo concern to the `logo` sub-resource and implies this is the write counterpart to beel_get_invoice_customization, but never says when to prefer it over siblings such as beel_list_invoice_customization_options or beel_patch_company. Usage is inferable from the resource name rather than stated.

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

Deploy Server

beel_update_invoice_customization

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools