Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_list_members

Read-onlyIdempotent

Get a paginated list of account members with their account roles and company NIFs for members. Use page and limit to control result size.

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.

Endpoint: GET /v1/accounts/{account_id}/members

Input Schema

TableJSON 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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds meaningful behavioral context beyond those: pagination defaults, the fact that only the first 20 members are returned without page/limit, and the guidance to read data.pagination to traverse the full result set.

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 description is compact and well-structured: the purpose comes first, pagination behavior follows, and the endpoint is given last. Every sentence contributes useful information with 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?

For a read-only list tool with no output schema, the description covers the essential details: what is returned, pagination defaults, and how to navigate additional pages via data.pagination. It could be slightly more explicit about the exact response container shape, but the provided guidance is sufficient for correct invocation.

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 the baseline is 3. The description reinforces the page/limit behavior and points to data.pagination, which slightly supplements the schema, but it does not add new parameter-level meaning beyond what the schema already documents.

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 states a specific verb and resource: 'Lists the people with access to the account' and details the included fields (account_role, granted companies/NIFs for MEMBERs). It is clear enough to distinguish from beel_get_member and beel_list_member_grants, though it does not name those alternatives explicitly.

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 description implies usage for listing account members and provides strong pagination usage guidance ('without them you get the first 20 members, not all of them. Read data.pagination to walk the rest.'). However, it does not explicitly state when to use this over sibling tools like beel_get_member or beel_list_member_grants.

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