Skip to main content
Glama
matthewbergvinson

Fathom MCP Server

list_meetings

Retrieve meeting records from Fathom.video with filtering options for date ranges, external participants, and quantity limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of meetings to return (default: 10, use 0 for all)
created_afterNoISO 8601 timestamp - only return meetings after this date
created_beforeNoISO 8601 timestamp - only return meetings before this date
include_external_onlyNoOnly include meetings with external participants

Implementation Reference

  • Primary handler implementation for the 'list_meetings' MCP tool. Registers the tool with input schema (Zod), destructures params, calls FathomClient.listMeetings with mapped filters, applies client-side limit slicing, formats output using formatMeetingList, and returns markdown text content.
    server.tool(
      'list_meetings',
      {
        limit: z.number().optional().describe('Maximum number of meetings to return (default: 10, use 0 for all)'),
        created_after: z.string().optional().describe('ISO 8601 timestamp - only return meetings after this date'),
        created_before: z.string().optional().describe('ISO 8601 timestamp - only return meetings before this date'),
        include_external_only: z.boolean().optional().describe('Only include meetings with external participants'),
      },
      async ({ limit, created_after, created_before, include_external_only }) => {
        console.error('Fetching meetings...');
        
        const response = await fathom.listMeetings({
          created_after,
          created_before,
          calendar_invitees_domains_type: include_external_only ? 'one_or_more_external' : undefined,
        });
    
        let meetings = response.items;
        if (limit && limit > 0) {
          meetings = meetings.slice(0, limit);
        }
    
        console.error(`Found ${meetings.length} meetings`);
        const markdown = formatMeetingList(meetings);
        
        return {
          content: [{ type: 'text', text: markdown }],
        };
      }
    );
  • TypeScript interface defining all possible parameters for listing meetings via Fathom API. Used by the tool handler to construct API request params (maps tool params to subset: created_after/before, calendar_invitees_domains_type).
    export interface ListMeetingsParams {
      include_transcript?: boolean;
      include_summary?: boolean;
      include_action_items?: boolean;
      include_crm_matches?: boolean;
      created_after?: string;
      created_before?: string;
      recorded_by?: string[];
      teams?: string[];
      calendar_invitees?: string[];
      calendar_invitees_domains?: string[];
      calendar_invitees_domains_type?: 'all' | 'only_internal' | 'one_or_more_external';
      cursor?: string;
    }
  • FathomClient helper method invoked by the tool handler. Builds query string from ListMeetingsParams and makes authenticated GET request to Fathom API /meetings endpoint.
    async listMeetings(params: ListMeetingsParams = {}): Promise<MeetingsResponse> {
      const searchParams = new URLSearchParams();
      
      if (params.include_transcript) searchParams.append('include_transcript', 'true');
      if (params.include_summary) searchParams.append('include_summary', 'true');
      if (params.include_action_items) searchParams.append('include_action_items', 'true');
      if (params.include_crm_matches) searchParams.append('include_crm_matches', 'true');
      if (params.created_after) searchParams.append('created_after', params.created_after);
      if (params.created_before) searchParams.append('created_before', params.created_before);
      if (params.cursor) searchParams.append('cursor', params.cursor);
      if (params.calendar_invitees_domains_type) {
        searchParams.append('calendar_invitees_domains_type', params.calendar_invitees_domains_type);
      }
      
      // Handle array params
      params.recorded_by?.forEach(email => searchParams.append('recorded_by[]', email));
      params.teams?.forEach(team => searchParams.append('teams[]', team));
      params.calendar_invitees?.forEach(email => searchParams.append('calendar_invitees[]', email));
      params.calendar_invitees_domains?.forEach(domain => searchParams.append('calendar_invitees_domains[]', domain));
    
      const queryString = searchParams.toString();
      const endpoint = `/meetings${queryString ? `?${queryString}` : ''}`;
      
      return this.request<MeetingsResponse>(endpoint);
    }
  • Utility function called by the tool handler to format the fetched meetings array into a markdown table with columns for title, date, duration, recorder, participant count, and ID.
    export function formatMeetingList(meetings: Meeting[]): string {
      if (meetings.length === 0) {
        return 'No meetings found.';
      }
    
      const rows = meetings.map(m => {
        const title = m.title || m.meeting_title || `Meeting ${m.recording_id}`;
        const date = formatDate(m.recording_start_time);
        const duration = formatDuration(m.recording_start_time, m.recording_end_time);
        const recorder = m.recorded_by.name;
        const participants = m.calendar_invitees.length;
        
        return `| ${title} | ${date} | ${duration} | ${recorder} | ${participants} | ${m.recording_id} |`;
      });
    
      return [
        '| Title | Date | Duration | Recorded By | Participants | ID |',
        '|-------|------|----------|-------------|--------------|-----|',
        ...rows,
      ].join('\n');
    }
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