Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_delete_customers_bulk

DestructiveIdempotent

Delete multiple customers for a company by ID in a single bulk operation. Customers with invoices are retained and returned with a status explaining why deletion failed.

Instructions

Deletes the customers listed in ids from this company.

Partial results

  • Partial operation: the customers that can be deleted are deleted, and the rest keep their place in customers_deletion with the status that explains why. That is why it answers 200 with a body instead of 204, and why it answers 200 even when no row could be deleted.

  • HAS_INVOICES: a customer that has invoices cannot be deleted and comes back with that row status.

What deleting means

  • Semantics: the same semantics as DELETE /v1/companies/{company_id}/customers/{customer_id} — the customer is retained internally for tax record-keeping purposes but is no longer exposed by the API, its identifier is released for reuse, and invoices already issued to it keep their own copy of the recipient's details.

  • Deleting is not deactivating: deleting frees the identifier, so the same NIF can be registered again, while PATCH with active: false leaves the customer where it is with its NIF still taken.

BeeL API endpoint: DELETE /v1/companies/{company_id}/customers/bulk (reference: https://docs.beel.es)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>",
      "ids": "<ids>"
    },
    "name": "beel_delete_customers_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesComma-separated customer IDs
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • 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."
    • removedInput schema / properties / ids / example
      Removed value: -"550e8400-e29b-41d4-a716-446655440000,550e8400-e29b-41d4-a716-446655440001"
  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?

Goes well beyond the destructive/idempotent hints by disclosing that the endpoint returns `200` with a body even on full failure, that successes and failures are mixed in `customers_deletion` with per-row statuses, and which status blocks deletion (`HAS_INVOICES`). It also spells out the underlying data semantics: internal retention for tax records, identifier release for NIF reuse, and invoice copies of recipient data.

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 opening sentence carries the core action, and the headed sections are scannable and information-dense rather than padded. It runs long, but nearly every line (partial-result semantics, row statuses, delete-vs-deactivate) changes how an agent would call or interpret the tool.

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

Completeness5/5

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

With no output schema, the description takes on the burden of explaining return behavior and does so concretely: `200` with a `customers_deletion` body, per-row statuses, and the `HAS_INVOICES` case. For a destructive bulk operation, that is sufficient for correct invocation and result interpretation.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning to `ids` by explaining that each entry is processed independently and reported back with a status rather than aborting the batch. `company_id` is already exhaustively documented in the schema and the description correctly refrains from repeating it.

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?

Opens with a specific verb and resource ('Deletes the customers listed in `ids` from this company'), making the bulk scope explicit through the `ids` list. The 'Deleting is not deactivating' section additionally separates it from `beel_patch_customer` and by implication from the single-customer `beel_delete_customer`.

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?

Gives clear when-to-use context: use it with a set of IDs, expect partial success, and expect `HAS_INVOICES` rows to be refused. It does not explicitly route single-customer deletions to `beel_delete_customer`, but the surrounding conditions are clear enough that an agent can pick correctly.

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