Skip to main content
Glama

List agents

list_agents
Read-onlyIdempotent

List the agents and administrators of this account (id, name, email, role, availability). Platform staff accounts are not listed, except on Hellou internal accounts, where they cannot be removed. Call before inviting, removing or changing the role of a person, or adding someone to an inbox or team.

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": "list_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds real value beyond them: it discloses an exclusion rule (platform staff accounts are omitted) and an exception for Hellou internal accounts where such accounts cannot be removed. That signals result incompleteness the agent would otherwise not expect. It does not describe ordering or result size, but no pagination parameters exist.

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?

Two tightly packed sentences: what it returns first, then when to call it. The staff-account exception clause is a slightly tangled parenthetical, but no sentence is filler.

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 simple, parameterless-filter read tool with 100% schema coverage and no output schema, the description covers identity, returned fields, exclusion behavior, and call timing. Nothing required to invoke it correctly is missing; only ordering and volume expectations are unstated.

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 coverage is 100% for the single optional 'fields' parameter, so the enum already documents selectable fields and their meaning. The parenthetical field list ('id, name, email, role, availability') loosely implies a default projection but drifts from the schema's 'availability_status' naming. Baseline 3 applies since the schema does the heavy lifting.

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 and resource ('List the agents and administrators of this account') and enumerates the returned attributes, so the agent knows exactly what comes back. It scopes the resource to 'this account', which implicitly separates it from the ElevenLabs agent lister, but it never names or explicitly contrasts with that sibling.

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 concrete triggering conditions: call before inviting, removing, changing a role, or adding someone to an inbox or team. This is genuinely actionable prerequisite guidance. It lacks any when-not-to-use statement or a named alternative for related lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources