Skip to main content
Glama

list_team_members

Retrieve team member information from Fathom AI MCP, with options to filter by team name and paginate results for efficient viewing.

Instructions

List team members, optionally filtered by team name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoTeam name to filter by.
pageNoPage number (starts at 1). Any page can be requested directly.
page_sizeNoNumber of members per page (default 10).

Implementation Reference

  • The actual API client method that fetches the team members data.
    async listTeamMembers(
      options: {
        team?: string | null;
        cursor?: string | null;
      } = {}
    ): Promise<Record<string, unknown>> {
      return this._get('/team_members', { cursor: options.cursor, team: options.team });
    }
  • src/server.ts:543-562 (registration)
    Registration of the 'list_team_members' tool including its schema.
    server.registerTool(
      'list_team_members',
      {
        description: 'List team members, optionally filtered by team name.',
        inputSchema: {
          team: z.string().optional().describe('Team name to filter by.'),
          page: z
            .number()
            .int()
            .min(1)
            .default(1)
            .describe('Page number (starts at 1). Any page can be requested directly.'),
          page_size: z
            .number()
            .int()
            .min(1)
            .default(DEFAULT_PAGE_SIZE)
            .describe('Number of members per page (default 10).'),
        },
      },
  • Tool handler in src/server.ts which uses the Fathom client to fetch the data.
    async args => {
      const client = getClient();
      const key = cacheKey('list_team_members', { team: args.team });
    
      let cached = _itemsCache.get(key);
      const isExpired = cached !== undefined && Date.now() - cached.fetchedAt > CACHE_TTL_MS;
      if (!cached || isExpired) {
        try {
          const result = await fetchAll(
            opts => client.listTeamMembers(opts as Record<string, unknown>),
            { team: args.team }
          );
Behavior2/5

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

With no annotations provided, the description carries full burden but reveals little behavioral detail. It mentions filtering capability but doesn't disclose pagination behavior (implied by parameters), rate limits, authentication requirements, or whether it's read-only/destructive. For a list tool with zero annotation coverage, this is insufficient transparency.

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?

The description is extremely concise—a single sentence that directly states the tool's function and primary optional filter. There's no wasted language, and it's front-loaded with the core purpose. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (list operation with filtering/pagination), no annotations, and no output schema, the description is minimally adequate but incomplete. It covers the basic purpose and filtering but omits behavioral context (e.g., pagination details, return format) that would help the agent use it effectively.

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 description coverage is 100%, so parameters are well-documented in the schema itself. The description adds marginal value by mentioning the 'team' filter option, but doesn't elaborate on parameter interactions or usage nuances beyond what the schema provides. This meets the baseline for high schema coverage.

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?

The description clearly states the verb ('List') and resource ('team members'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'list_teams' by focusing on members rather than teams. However, it doesn't specify whether this includes all members across all teams or just active members, leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides minimal guidance with 'optionally filtered by team name,' but offers no explicit when-to-use advice. It doesn't differentiate from potential alternatives (e.g., when to use this vs. 'get_summary' for member overviews) or mention prerequisites like authentication needs. This leaves the agent with little context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jerichosequitin/fathom-ai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server