Skip to main content
Glama
Sign In
BeeL MCP server

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_list_members

Read-onlyIdempotent

Lists account members, showing their account roles and assigned company NIFs for MEMBER users. Supports pagination so you can retrieve every member beyond the first 20.

Instructions

Lists the people with access to the account, each with their account_role and, for MEMBERs, the companies (NIFs) granted to them.

Paginated with the usual page/limit, and the usual defaults: without them you get the first 20 members, not all of them. Read data.pagination to walk the rest.

BeeL API endpoint: GET /v1/accounts/{account_id}/members (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": {
      "account_id": "<account_id>"
    },
    "name": "beel_list_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. The response echoes it back as `pagination.current_page`.
limitNoHow many items to return per page. The response echoes it back as `pagination.items_per_page`.
account_idYesYour own account, or an account you provisioned. It — not the credential — decides which account the operation acts on; a `403` is returned when you do not reach it, the same response an account that does not exist gets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 20,
+  "description": "How many items to return per page. The response echoes it back as `pagination.items_per_page`.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Page number, starting at 1. The response echoes it back as `pagination.current_page`.",
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds value beyond that: the silent truncation at 20 items, the pointer to `data.pagination` for walking pages, and the conditional return field (company NIFs only for `MEMBER` roles). It does not mention permissions/403 behavior, though the schema's `account_id` description does.

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?

Front-loaded with the purpose and payload shape, followed by the pagination caveat, then the endpoint reference as a footer. The bolded 'Paginated' and the docs URL are slightly ornamental, but no sentence is wasted.

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?

With no output schema, the description carries the burden of describing returns and does so partially: role, conditional NIF grants, and the `data.pagination` envelope. A remaining ambiguity is whether pending invitees appear here or only in `beel_list_invitations`, which matters for correct tool selection.

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%, so both `page` and `limit` are already fully documented, making 3 the baseline. The description echoes the defaults but adds a consequence the schema does not spell out – that omitting them returns only the first 20 members – which is modest added meaning rather than new parameter semantics.

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?

States a specific verb ('Lists') and resource ('the people with access to the account') and even previews the payload shape: `account_role` plus granted companies (NIFs) for `MEMBER`s. That is enough to separate it from `beel_get_member` (single member) and `beel_list_member_grants`, but neither sibling is named, so the differentiation is inferred rather than stated.

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?

Gives real operational guidance about pagination ('without them you get the first 20 members, not all of them' and 'Read `data.pagination` to walk the rest'), which tells the agent how to consume results correctly. It gives no when-to-use-vs-alternative guidance, e.g. when to call this versus `beel_list_invitations` for pending people or `beel_list_member_grants` for grants alone.

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