Skip to main content
Glama
trevorwelch

Fathom Video MCP Server

by trevorwelch

list_meetings

Filter and list Fathom meetings by date, search terms, invitee domains, and more. Supports pagination and optional inclusion of AI summaries, transcripts, and action items.

Instructions

List Fathom meetings with optional filtering.

Returns a paginated list of meetings. Use the recording_id from the results to fetch summaries or transcripts with get_summary or get_transcript.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of meetings to return (1-50)
searchNoSmart search: matches titles, attendee names, and email domains (e.g., 'Acme' finds acme.com)
cursorNoPagination cursor from previous response
created_afterNoFilter meetings created after this ISO timestamp (e.g., 2025-01-01T00:00:00Z)
created_beforeNoFilter meetings created before this ISO timestamp (e.g., 2025-12-31T23:59:59Z)
include_summaryNoInclude AI-generated summary in the response
include_transcriptNoInclude full transcript in the response
include_action_itemsNoInclude action items in the response
recorded_byNoFilter by email addresses of users who recorded the meetings
teamsNoFilter by team names
calendar_invitees_domains_typeNoFilter by invitee type: 'all', 'only_internal', or 'one_or_more_external'
invitee_domainsNoFilter by invitee email domains (e.g., ['acme.com', 'example.com'])

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description must convey behavioral traits. It mentions pagination ('Returns a paginated list') and optional filtering, which discloses key behavior. It does not contradict any implicit safety assumptions.

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?

The description is two sentences, front-loading the purpose and then providing actionable guidance. Every sentence serves a clear function with no waste.

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

Completeness5/5

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

Given the tool has 12 parameters all documented in the schema and an output schema exists, the description covers the essential behavior (pagination, filtering, follow-up actions) without needing to duplicate schema details. It is complete for a listing endpoint.

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?

With 100% schema description coverage, the parameter descriptions in the schema are already detailed. The tool description adds no new semantic meaning beyond stating 'optional filtering' and mentioning pagination, which is already implied.

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

Purpose5/5

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

The description clearly states 'List Fathom meetings with optional filtering,' which is a specific verb and resource. It also distinguishes from sibling tools by mentioning how to use recording_id with get_summary or get_transcript.

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?

The description explicitly tells when to use get_summary or get_transcript after listing meetings, providing clear context. It does not include exclusions or alternative use cases, but the guidance is clear.

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

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