Skip to main content
Glama

List Members

list_members
Read-onlyIdempotent

List the members of the workspace (the current one unless workspaceId names another). Returns { members } with userId, email, firstName, lastName, role (admin, editor, contributor or viewer in this workspace), organizationRoles (such as org-owner, org-admin or org-member) and joinedAt. Pass userId to remove_member or remove_organization_member. Needs the members.read permission, which every role holds. Takes only the optional workspaceId.

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
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with members: one { userId, email, firstName, lastName, role, organizationRoles, joinedAt } per member of the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds context the annotations cannot carry: the implicit current-workspace default, the members.read permission requirement, and the meaning of the role values within this workspace versus organizationRoles. It does not mention pagination or result limits, 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?

Front-loaded with the action and scope, then the return shape, the cross-tool handoff, and the permission note in a logical order with no filler. The enumeration of return fields is on the verbose side given an output schema exists, but it is scannable and not padded.

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 single-optional-parameter read tool with full annotations and an output schema, the description covers default scoping, permissions, role vocabulary, and the natural next tool. Only the absence of any note about result size or pagination keeps it from being fully complete.

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% and the single workspaceId parameter is already fully documented, including the cross-workspace id rule. The description's "takes only the optional workspaceId" and the current-workspace default largely restate the schema rather than adding syntax or format detail, so the baseline of 3 applies.

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?

States a specific verb and resource ("List the members of the workspace") and immediately bounds the scope to the current workspace unless workspaceId overrides it. This is clearly distinguishable from the remove_member siblings and from list_workspaces.

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 the follow-up path explicitly ("Pass userId to remove_member or remove_organization_member") and states the permission prerequisite plus the reassuring fact that every role holds it. It does not spell out a when-not-to-use case, but the read-only listing job has no realistic alternative among the siblings, so the guidance is effectively complete.

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