Skip to main content
Glama

List team members

listTeamMembers
Read-onlyIdempotent

List this company's team members on Clera plus any pending email invitations.

Returns each member's name, email, and role, and each pending invite's email, role, and invited date. Roles are owner, editor, or viewer. No internal ids are returned; refer to people by name or email.

Use this to check who already has access before inviting someone, so you don't re-invite an existing member or duplicate a pending invitation.

Clera privately records this tool's inputs and results for usage tracking and support.

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

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.

Output Schema

NameRequiredDescriptionDefault
membersYes
pendingInvitationsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. Beyond that the description adds real context: pending invitations are included in the result set, role values are owner/editor/viewer, and no internal ids are returned (refer to people by name or email). The privacy note about input/result recording is unusual but is a genuine behavioral disclosure.

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 core action, then return shape, then usage guidance, in four tight paragraphs. The closing sentence about recording inputs and results for usage tracking is the only one that is not task-essential, though it functions as a compliance disclosure.

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?

For a simple zero-required-parameter list tool with an output schema and full annotations, nothing an agent needs in order to call it correctly is missing: return fields, role values, absence of ids, and the intended use case are all stated.

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?

There is a single parameter (orgId) at 100% schema coverage, so the schema already documents it fully. The description's phrase 'this company's' only loosely implies organization scoping and adds nothing about the multi-org case that the schema description doesn't already state.

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 with scope: 'List this company's team members on Clera plus any pending email invitations.' It also enumerates the returned fields (name, email, role, invited date) and confirms no internal ids, which unambiguously separates it from the pipeline/job/candidate siblings.

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?

Explicit when-to-use is given: check existing access before inviting someone, to avoid re-inviting a member or duplicating a pending invite. There is no explicit when-not or named alternative, but no sibling in the catalog overlaps with team membership, so the guidance is sufficient in practice.

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