Skip to main content
Glama

list_members

Read-only

List everyone on the account: the members who have joined (name, email, account role, join date, whether they keep the default workspace, and their role in each client workspace), the invites still pending (with who sent them, when, and the workspace roles each one will hand over on accept), and how many seats the plan has left. Covers the whole account, not just the active workspace. Account admins only.

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_members"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish this is a non-destructive, closed-world read. The description adds the authorization constraint (account admins only) and enumerates the payload shape including derived data such as each invitee's future workspace roles and the plan's remaining seat count. It does not mention pagination or result-size behavior, which is the main remaining gap.

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?

A single front-loaded sentence with the most important fact (account-wide scope) first and the access restriction last. The parenthetical enumerations are dense but each item conveys real return-value information; a slightly tighter list format would read better.

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?

There is no output schema, so the description carries the full burden of explaining return values, and it does so thoroughly: member fields, pending-invite details, and seat count. Combined with the admin-only caveat and account-wide scope, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4; the description correctly makes no parameter claims and instead spends its words on scope and output content. Nothing about parameter semantics is missing or misleading.

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?

Opens with a concrete verb+resource ("List everyone on the account") and enumerates exactly what is returned: joined members, pending invites with senders and workspace roles, and remaining seats. This clearly separates it from sibling listers like list_workspaces, list_connected_accounts, and list_accounts, and from the mutating invite_member.

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?

States the crucial scoping rule explicitly ("Covers the whole account, not just the active workspace") and the access precondition ("Account admins only"), which are the main decisions for an agent. It stops short of naming invite_member as the alternative for adding people or list_workspaces for workspace-level rosters, so the contrast is implied rather than spelled out.

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