Skip to main content
Glama
Sign In
fathom-mcp-server

fathom-mcp-server

by luminarylane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fathom_get_transcript

Retrieve a complete, speaker-labeled transcript with timestamps for any meeting by providing its recording ID.

Instructions

Get the full speaker-labeled, timestamped transcript for a specific meeting. Use sparingly — transcripts can be large. Prefer fathom_list_meetings for quick overviews.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recording_id": "<recording_id>"
    },
    "name": "fathom_get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
recording_idYesThe meeting/recording ID from fathom_list_meetings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided; description mentions large size but does not disclose other behavioral traits such as read-only nature, latency, or output format beyond basic structure.

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?

Two sentences, no fluff. Front-loaded with purpose, followed by usage guidance. Every sentence earns its place.

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

Completeness4/5

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

Adequate for a simple one-parameter tool with no output schema. It explains what the tool returns and gives usage advice, though it could specify output format more precisely.

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 covers the only parameter (recording_id) fully. The tool description adds no additional meaning beyond restating the parameter name.

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?

Clearly states it retrieves a full transcript with speaker labels and timestamps. Does not explicitly differentiate from fathom_get_summary or fathom_search_meetings, only from fathom_list_meetings.

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

Usage Guidelines4/5

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

Provides explicit advice to use sparingly due to size and suggests an alternative for quick overviews (fathom_list_meetings). Does not address when to use other siblings like fathom_get_summary.

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

Deploy Server

Other Tools