Skip to main content
Glama
matthewbergvinson

Fathom MCP Server

get_transcript

Retrieve AI-generated meeting transcripts from Fathom.video recordings using the recording ID to access conversation content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recording_idYesThe recording ID of the meeting

Implementation Reference

  • The core execution logic (handler function) for the MCP 'get_transcript' tool. It fetches the transcript using the FathomClient and formats it to Markdown before returning as text content.
    async ({ recording_id }) => {
      console.error(`Fetching transcript for ${recording_id}...`);
      
      const response = await fathom.getTranscript(recording_id);
      const markdown = formatTranscriptToMarkdown(response.transcript);
      
      console.error('Transcript retrieved');
      return {
        content: [{ type: 'text', text: markdown }],
      };
    }
  • Input schema definition for the 'get_transcript' tool using Zod, requiring a numeric recording_id.
    {
      recording_id: z.number().describe('The recording ID of the meeting'),
    },
  • src/index.ts:127-143 (registration)
    Registration of the 'get_transcript' MCP tool on the McpServer instance, including name, input schema, and handler reference.
    server.tool(
      'get_transcript',
      {
        recording_id: z.number().describe('The recording ID of the meeting'),
      },
      async ({ recording_id }) => {
        console.error(`Fetching transcript for ${recording_id}...`);
        
        const response = await fathom.getTranscript(recording_id);
        const markdown = formatTranscriptToMarkdown(response.transcript);
        
        console.error('Transcript retrieved');
        return {
          content: [{ type: 'text', text: markdown }],
        };
      }
    );
  • FathomClient helper method that makes the API request to retrieve the transcript for a specific recording ID.
    async getTranscript(recordingId: number): Promise<TranscriptResponse> {
      return this.request<TranscriptResponse>(`/recordings/${recordingId}/transcript`);
    }
  • Utility function to format the raw transcript array into readable Markdown with speaker labels and timestamps.
    export function formatTranscriptToMarkdown(transcript: TranscriptItem[]): string {
      if (!transcript || transcript.length === 0) {
        return '_No transcript available_';
      }
    
      const lines: string[] = [];
      let currentSpeaker = '';
    
      for (const item of transcript) {
        const speakerName = item.speaker.display_name || 'Unknown Speaker';
        
        // Add speaker header when speaker changes
        if (speakerName !== currentSpeaker) {
          currentSpeaker = speakerName;
          lines.push('');
          lines.push(`**${speakerName}** _[${formatTimestamp(item.timestamp)}]_`);
        }
        
        lines.push(`> ${item.text}`);
      }
    
      return lines.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