Skip to main content
Glama

List people

members_list
Read-only

List the organization's people, by name, a page at a time: each one's user_id, name, handle, role (owner or member) and when they joined, with the total. An organization's owners also read each person's email. Narrow with query or role; continue with offset.

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": {
      "org": "<org>"
    },
    "name": "members_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it.
roleNoOnly people at this role in the organization.
limitNoPeople per page; 50 when left out.
queryNoNarrow to people whose name or email matches.
offsetNoHow many people to skip, to continue past a page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / org / description
      Previous value: -"slug of the organization whose people, teams and access to read. Required on every call, even when only one organization is listed; a path never names it."New value: +"slug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/non-destructive annotations, the description discloses two substantive traits: results come paginated with a total count, and email is only returned when the caller is an organization owner. That access-conditioning detail is real behavioral context an agent could not get from annotations alone.

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?

The payload is front-loaded in a single dense sentence, with the filtering and paging hints trailing as short fragments. Nearly every clause carries information, though the middle enumeration of five fields is slightly list-like and could be tightened.

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 usefully compensates by naming the returned fields and the total. For a read-only paginated list tool with fully documented parameters and clear safety annotations, the only missing piece is any return-shape detail for the paging envelope (e.g. how the total is surfaced).

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%, so all five parameters are already documented in structured fields, including the 50-item default for limit and the owner/member enum for role. The description restates narrowing and continuation but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 organization's people') and enumerates the returned fields (user_id, name, handle, role, joined, total), so the agent knows exactly what this yields. It does not explicitly contrast itself with nearby siblings like team_list or access_person, which keeps it short of a 5.

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?

'Narrow with query or role; continue with offset' gives concrete usage mechanics for refining and paging. However, there is no statement of when to prefer this over alternatives such as access_person for a single person, nor any stated exclusions, so guidance is implied rather than explicit.

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