Skip to main content
Glama
matthewbergvinson

Fathom MCP Server

list_teams

Retrieve and display all teams from Fathom.video meeting data to manage access and organize meeting information efficiently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:332-355 (registration)
    Registers the 'list_teams' MCP tool with empty input schema. The inline handler fetches all teams using fathom.getAllTeams(), formats them into a markdown list with creation dates, and returns as structured content.
    server.tool(
      'list_teams',
      {},
      async () => {
        console.error('Fetching teams...');
        const teams = await fathom.getAllTeams();
    
        if (teams.length === 0) {
          return {
            content: [{ type: 'text', text: 'No teams found.' }],
          };
        }
    
        const markdown = teams.map(t => {
          const created = formatDate(t.created_at);
          return `- **${t.name}** (created: ${created})`;
        }).join('\n');
    
        console.error(`Found ${teams.length} teams`);
        return {
          content: [{ type: 'text', text: `# Teams\n\n${markdown}` }],
        };
      }
    );
  • The handler function for the list_teams tool. Retrieves all teams, handles empty case, maps to markdown bullets with formatted dates using formatDate, logs count, and returns markdown text content.
    async () => {
      console.error('Fetching teams...');
      const teams = await fathom.getAllTeams();
    
      if (teams.length === 0) {
        return {
          content: [{ type: 'text', text: 'No teams found.' }],
        };
      }
    
      const markdown = teams.map(t => {
        const created = formatDate(t.created_at);
        return `- **${t.name}** (created: ${created})`;
      }).join('\n');
    
      console.error(`Found ${teams.length} teams`);
      return {
        content: [{ type: 'text', text: `# Teams\n\n${markdown}` }],
      };
    }
  • Helper method in FathomClient that paginates the /teams API endpoint using listTeams() to collect and return all teams.
    async getAllTeams(): Promise<Team[]> {
      const allTeams: Team[] = [];
      let cursor: string | null | undefined = undefined;
    
      do {
        const response = await this.listTeams(cursor || undefined);
        allTeams.push(...response.items);
        cursor = response.next_cursor;
      } while (cursor);
    
      return allTeams;
    }
  • Low-level API method that calls the Fathom /teams endpoint, supporting cursor for pagination.
    async listTeams(cursor?: string): Promise<TeamsResponse> {
      const endpoint = cursor ? `/teams?cursor=${cursor}` : '/teams';
      return this.request<TeamsResponse>(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