Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_create_products_bulk

Idempotent

Creates up to 100 products in a company catalog in one request. Each product is processed independently, so invalid rows are reported while valid products are still created.

Instructions

Creates up to 100 products in the catalog of this company.

  • Partial operation: each product is processed and reported independently, so a row the domain rejects — a rate the law does not allow, a duplicate code — comes back inside the report while the rest are created.

  • Status code: always 201 when the batch was processed, even if not a single product could be created. A malformed request — a missing field, an empty array, more than 100 items — answers 422 instead and nothing is processed.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
company_idYesUnique 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_keyNoOptional 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.

  1. Changed17 schema fields changedv0.5.0
    • 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
    • addedInput schema / properties / body / 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."
  2. First observedv0.3.1

TDQS

A4.2/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing two non-obvious behaviors: partial operation with independent per-row reporting, and the always-201-on-processed behavior even when zero products are created. The 422 malformed-request case is also clearly distinguished. No contradiction with annotations.

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 core purpose is front-loaded in one sentence, and the two bullets each add high-value non-obvious behavior. The endpoint line is useful context. There is no filler or redundancy.

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?

The description covers operation semantics, limits, and status codes well. However, with no output schema present, it stops at 'comes back inside the report' without describing the shape or fields of the per-item report, which an agent would need to reliably interpret partial success.

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?

Top-level schema coverage is 67%: company_id and idempotency_key are well described, but the body parameter itself has no description. The description adds the array size limit and the empty-batch 422 behavior, but does not explain the per-row report structure that the partial-operation semantics depend on.

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 specific verb ('Creates'), a specific resource ('products in the catalog of this company'), and a hard limit ('up to 100'). This makes the tool immediately distinguishable from beel_create_product and the many other create_* sibling tools.

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?

Bulk semantics and the 100-item limit imply this is for batch creation, but there is no explicit guidance such as 'use beel_create_product for a single product' or 'use this when creating multiple products at once.' The intended usage is inferable but not stated.

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

Deploy Server

Other Tools