BeeL MCP server

Official

Overview Schema Source Related Servers Discussions Admin

beel_create_product

Idempotent

Create a product or service in the company catalog, defining category, price, tax, and withholding data for use in compliant Spanish electronic invoicing.

Instructions

Creates a new product or service in the catalog of this company.

Endpoint: POST /v1/companies/{company_id}/products

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`idempotency_key`	No	Optional 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.

Changed16 schema fields changedv0.5.0Aug 30, 2026

addedInput schema / $defs / CreateProductRequest / additionalProperties
```
Added value: +false
```
removedInput schema / $defs / CreateProductRequest / properties / code / example
```
Removed value: -"SERV-001"
```
removedInput schema / $defs / CreateProductRequest / properties / default_price / example
```
Removed value: -85.5
```
removedInput schema / $defs / CreateProductRequest / properties / description / example
```
Removed value: -"Specialized technical consulting services"
```
removedInput schema / $defs / CreateProductRequest / properties / equivalence_surcharge_rate / example
```
Removed value: -5.2
```
removedInput schema / $defs / CreateProductRequest / properties / irpf_rate / example
```
Removed value: -15
```
removedInput schema / $defs / CreateProductRequest / properties / name / example
```
Removed value: -"Technical consulting"
```
removedInput schema / $defs / CreateProductRequest / properties / unit / example
```
Removed value: -"hours"
```
removedInput schema / $defs / ProductCategory / example
```
Removed value: -"CONSULTING"
```
removedInput schema / $defs / RegimeKey / example
```
Removed value: -"01"
```
addedInput schema / $defs / TaxInfo / additionalProperties
```
Added value: +false
```

removedInput schema / $defs / TaxInfo / example

Removed value: -{
-  "percentage": 21,
-  "regime_key": "01",
-  "type": "IVA"
-}

removedInput schema / $defs / TaxInfo / properties / percentage / example
```
Removed value: -21
```
removedInput schema / $defs / TaxType / example
```
Removed value: -"IVA"
```
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

A3.5/5.0

Behavior3/5

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

Annotations already cover readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds only the endpoint and does not mention idempotency collision behavior, though the schema documents it.

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?

Two sentences with no filler: the purpose is front-loaded and the endpoint is a useful secondary detail. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimal but sufficient for basic invocation given the annotations and rich schema. However, it omits routing guidance to the bulk creation sibling and does not indicate what a successful response contains, which matters since there is no output schema.

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 adds no parameter semantics beyond what the input schema already provides. With 67% schema description coverage and the body schema containing extensive tax and product details, the description does not need to compensate.

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 uses a specific verb and resource: 'Creates a new product or service in the catalog of this company' and provides the endpoint. It clearly identifies the operation, but it does not explicitly differentiate from the sibling beel_create_products_bulk.

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?

The action sentence implies the tool is for creating a single product or service, but there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives like beel_create_products_bulk.

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

Deploy Server

beel_create_product

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools