Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_list_accounts

Read-onlyIdempotent

Returns the accounts you provisioned, newest first. Filter by lifecycle status or external reference, and paginate with a cursor.

Instructions

Returns the accounts you provisioned, newest first. Each carries its lifecycle status (PROVISIONED → CLAIMED → ACTIVE), the access_level you hold over it and the state of its claim link.

  • status: narrows the list to one lifecycle stage.

  • external_ref: looks an account up by the reference you assigned when provisioning it; returns the 0..1 matching accounts.

Cursor pagination. This collection pages by cursor/next_cursor instead of by page, so it carries no pagination block. That is a documented variant of pagination, not a different envelope: the collection still travels under a named key inside data. Keep asking with the next_cursor of the previous response until it comes back null.

BeeL API endpoint: GET /v1/accounts (reference: https://docs.beel.es)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "beel_list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of accounts to return per page (1–200). Defaults to 50.
cursorNoOpaque pagination cursor from a previous response's `next_cursor`.
statusNoKeeps only the accounts at this lifecycle stage. Omitted, every stage is listed.
external_refNoYour own id for the account; returns the 0..1 matching accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / status / type
      Added value: +"string"
  2. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / status / description
      Added value: +"Keeps only the accounts at this lifecycle stage. Omitted, every stage is listed."
  3. Changed1 schema field changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observedv0.3.1

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses ordering ('newest first'), lifecycle status semantics, external_ref lookup behavior, and the cursor/next_cursor pagination variant with its envelope implications. That is substantial behavioral context for a read-only list operation.

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 front-loaded with the core purpose, then uses compact bullets for the filters and a focused paragraph for the nonstandard cursor pagination. Despite some detail about the pagination envelope, every section helps the agent call the tool correctly.

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 still explains what each returned account carries, the ordering, the external_ref cardinality, and how to paginate via next_cursor. For a read-only listing tool with fully documented parameters, that is complete enough 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 parameter meanings are already fully documented in the schema. The description restates the status and external_ref behavior and adds cursor/next_cursor response context, but it does not meaningfully extend the parameter semantics beyond what the schema already provides.

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 opening sentence gives a specific verb and resource: 'Returns the accounts you provisioned, newest first.' It also states the ordering and scope, which distinguishes it from sibling tools like beel_get_account (single account) and beel_provision_account (create account).

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 explains what the status and external_ref filters do and how cursor pagination works, but it does not explicitly say when to use this list tool versus alternatives such as beel_get_account for a single account. Usage is implied rather than framed as when/when-not guidance.

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