Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_delete_products_bulk

DestructiveIdempotent

Delete up to 100 company catalog products per request. Get a detailed response showing which product IDs were deleted and which failed, with summary counts.

Instructions

Deletes the products listed in ids from the catalog of this company, up to 100 IDs per request; send several requests for more.

  • Partial operation: the response reports which products were deleted (deleted_products) and which failed (errors, one entry per product with its product_id), with the counts in summary. That is why it answers 200 with a body instead of 204.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesComma-separated product IDs (max 100 per request)
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/5.0
Behavior4/5

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

Annotations already mark the operation as destructive and non-read-only, and the description adds meaningful behavioral detail: partial operation, per-item success/failure reporting through `deleted_products` and `errors`, `summary` counts, and why HTTP 200 with a body is returned instead of 204. This goes beyond annotations and helps the agent set expectations.

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?

Core action, batch limit, response semantics, and endpoint are presented in a compact, front-loaded structure. No filler or repetitive content; the bullet formatting improves scannability.

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?

Even though there is no output schema, the description explains the response shape and counts sufficiently, and the schema covers both parameters in detail. The main omission is explicit retry/idempotency behavior, but the idempotentHint annotation covers that. Overall an agent has what it needs to invoke the tool 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?

Schema description coverage is 100%, and the schema entries already explain the comma-separated `ids` format and the UUID `company_id` semantics, including the 403 behavior. The tool description itself does not add new parameter-level meaning beyond what the schema provides, so baseline 3 applies.

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 the operation explicitly: deleting products listed in `ids` from the company catalog, with a bulk limit. The 'up to 100 IDs' phrasing and endpoint underscore the batch nature, distinguishing it from single-product deletion siblings. This is specific and actionable.

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?

Describes the request size limit and instructs sending multiple requests beyond 100 IDs, which is practical usage guidance. However, it does not explicitly mention alternatives such as `beel_delete_product` for single deletions or contrast when bulk vs single should be chosen. The context is clear but exclusions are left implicit.

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