Skip to main content
Glama
matthewbergvinson

Fathom MCP Server

list_team_members

Retrieve team member information from Fathom meeting data to manage collaboration and access permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoFilter by team name

Implementation Reference

  • The handler function that implements the core logic of the 'list_team_members' tool. It fetches team members using the FathomClient and formats them into a markdown list.
    async ({ team }) => {
      console.error(team ? `Fetching members for team: ${team}...` : 'Fetching all team members...');
      const members = await fathom.getAllTeamMembers(team);
    
      if (members.length === 0) {
        return {
          content: [{ type: 'text', text: team ? `No members found in team "${team}".` : 'No team members found.' }],
        };
      }
    
      const markdown = members.map(m => `- **${m.name}** <${m.email}>`).join('\n');
      const title = team ? `Team Members: ${team}` : 'All Team Members';
    
      console.error(`Found ${members.length} members`);
      return {
        content: [{ type: 'text', text: `# ${title}\n\n${markdown}` }],
      };
    }
  • Zod schema defining the input parameters for the list_team_members tool (optional team filter).
    {
      team: z.string().optional().describe('Filter by team name'),
    },
  • src/index.ts:360-383 (registration)
    Registration of the 'list_team_members' tool on the MCP server using server.tool(), including schema and handler.
    server.tool(
      'list_team_members',
      {
        team: z.string().optional().describe('Filter by team name'),
      },
      async ({ team }) => {
        console.error(team ? `Fetching members for team: ${team}...` : 'Fetching all team members...');
        const members = await fathom.getAllTeamMembers(team);
    
        if (members.length === 0) {
          return {
            content: [{ type: 'text', text: team ? `No members found in team "${team}".` : 'No team members found.' }],
          };
        }
    
        const markdown = members.map(m => `- **${m.name}** <${m.email}>`).join('\n');
        const title = team ? `Team Members: ${team}` : 'All Team Members';
    
        console.error(`Found ${members.length} members`);
        return {
          content: [{ type: 'text', text: `# ${title}\n\n${markdown}` }],
        };
      }
    );
  • FathomClient helper method that handles pagination to retrieve all team members for a specific team or all teams.
    async getAllTeamMembers(team?: string): Promise<TeamMember[]> {
      const allMembers: TeamMember[] = [];
      let cursor: string | null | undefined = undefined;
    
      do {
        const response = await this.listTeamMembers(team, cursor || undefined);
        allMembers.push(...response.items);
        cursor = response.next_cursor;
      } while (cursor);
    
      return allMembers;
    }
  • FathomClient method that makes the API request to list team members with optional team filter and pagination cursor.
    async listTeamMembers(team?: string, cursor?: string): Promise<TeamMembersResponse> {
      const params = new URLSearchParams();
      if (team) params.append('team', team);
      if (cursor) params.append('cursor', cursor);
      
      const queryString = params.toString();
      const endpoint = `/team_members${queryString ? `?${queryString}` : ''}`;
      
      return this.request<TeamMembersResponse>(endpoint);
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/matthewbergvinson/fathom-mcp'

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