BeeL MCP server

Official

Overview Schema Source Related Servers Discussions Admin

beel_update_invoice_customization

Idempotent

Update a company's invoice customization to control PDF template, accent color, invoice language, and email language. Only supplied properties are changed, and new settings apply to invoices issued after the update.

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.

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 mark this as non-read-only, non-destructive, and idempotent, so the description's job is lighter. It adds valuable behavior beyond annotations: only present properties are modified, the logo is handled elsewhere, and changes affect only future invoices without altering already issued documents. These are exactly the operational traits an agent needs to predict side effects.

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 compact and front-loaded with purpose, followed by the key partial-update and temporal-scope behaviors, then the endpoint for grounding. The partial-update sentence slightly duplicates the schema's body description, but it is important enough to warrant reinforcement and does not bloat 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 essential behavioral ground: what is updated, partial-update semantics, logo routing, and the temporal scope of the change. It does not describe the response format, but the invocation path and expected effects are sufficiently complete for an agent to call it correctly.

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?

The description names the four updatable fields, but the schema itself already describes each property and the partial-update semantics in UpdateInvoiceCustomizationRequest. The company_id parameter is richly explained in the schema, and the description adds little parameter-level meaning beyond restating the field list. Schema coverage is moderate, yet the schema descriptions already do the heavy lifting.

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 opens with a specific verb and resource: it updates how a company's invoices are rendered and delivered, then enumerates the exact fields (PDF template, accent colour, invoice language, email language). This clearly distinguishes it from the read-style siblings such as beel_get_invoice_customization and beel_list_invoice_customization_options.

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 establishes clear usage context: it is a partial update that only touches properties present in the body, and it explicitly routes logo changes to the `logo` sub-resource instead of this tool. It does not explicitly name sibling alternatives, but the partial-update and logo exclusions give an agent enough guidance for correct selection.

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