Skip to main content
Glama

List workspace members

list_members
Read-only

Retrieves everyone in a Recordful workspace, including name, email, and role (owner or member), plus invited email addresses that haven't joined yet. Read-only; requires Recordful Pro.

Instructions

Recordful Pro only (check get_status recorder.account.plan first). Who is in the user's Recordful workspace (name, email, role: owner or member) and which email addresses are invited but haven't joined. Read-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. Addedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds the non-obvious Pro-plan eligibility gate and the exact shape of returned data (role values, pending invites). The closing 'Read-only' is redundant with the annotation but the plan gating is genuine added context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the eligibility gate front-loaded before the content description. Only the trailing 'Read-only' restates the annotation and is slightly wasted, but overall there is no padding.

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 parameters and no output schema, the description usefully enumerates what comes back and the one blocking prerequisite. Minor gaps remain about ordering or size limits for large workspaces, but nothing an agent needs to invoke it correctly is absent.

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?

The tool takes zero parameters, so the baseline applies and there is no parameter meaning the description needed to supply. Nothing is missing on this dimension.

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 resource and its exact contents: workspace members with name, email, and role (owner/member), plus invited-but-not-joined emails. That level of specificity also separates it from sibling listing tools such as list_recordings or list_videos.

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 an explicit precondition ('Recordful Pro only', verify via get_status recorder.account.plan first), which is real when-to-use guidance an agent can act on. It does not name an alternative for the non-Pro case or for people-search scenarios, so it falls short of full when/when-not coverage.

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