Fathom-Simple-MCP

by druellan

Overview Schema Source Related Servers Discussions Admin

Python

list_meetings

Read-only

Retrieve paginated meetings filtered by team, date, or invitee, with optional action items and CRM matches.

Instructions

Retrieve paginated meetings with filtering and optional content inclusion (action items, CRM matches).

Examples: list_meetings() # Get all meetings (paginated) list_meetings(created_after="2024-01-01T00:00:00Z") # Meetings after specific date list_meetings(teams=["Sales", "Engineering"]) # Filter by specific teams list_meetings(calendar_invitees=["john.doe@company.com", "jane.smith@client.com"]) # Filter by specific attendees list_meetings(calendar_invitees_domains=["company.com", "client.com"]) # Filter by attendee domains

Input Schema

TableJSON Schema

Name	Required	Description
`teams`	No
`cursor`	No
`per_page`	No	Number of results per page (default: 50)
`recorded_by`	No
`created_after`	No
`created_before`	No
`calendar_invitees`	No
`include_crm_matches`	No
`include_action_items`	No
`calendar_invitees_domains`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed32 schema fields changedv0.2.0Jul 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / calendar_invitees / anyOf

Added value: +[
+  {
+    "description": "Filter by invitee emails",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / calendar_invitees / description
```
Removed value: -"Filter by invitee emails"
```
removedInput schema / properties / calendar_invitees / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / calendar_invitees / type
```
Removed value: -"array"
```

addedInput schema / properties / calendar_invitees_domains / anyOf

Added value: +[
+  {
+    "description": "Filter by domains",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / calendar_invitees_domains / description
```
Removed value: -"Filter by domains"
```
removedInput schema / properties / calendar_invitees_domains / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / calendar_invitees_domains / type
```
Removed value: -"array"
```

addedInput schema / properties / created_after / anyOf

Added value: +[
+  {
+    "description": "ISO timestamp filter",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / created_after / description
```
Removed value: -"ISO timestamp filter"
```
removedInput schema / properties / created_after / type
```
Removed value: -"string"
```

addedInput schema / properties / created_before / anyOf

Added value: +[
+  {
+    "description": "ISO timestamp filter",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / created_before / description
```
Removed value: -"ISO timestamp filter"
```
removedInput schema / properties / created_before / type
```
Removed value: -"string"
```

addedInput schema / properties / cursor / anyOf

Added value: +[
+  {
+    "description": "Pagination cursor",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / cursor / description
```
Removed value: -"Pagination cursor"
```
removedInput schema / properties / cursor / type
```
Removed value: -"string"
```

addedInput schema / properties / include_action_items / anyOf

Added value: +[
+  {
+    "description": "Include action items",
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / include_action_items / description
```
Removed value: -"Include action items"
```
removedInput schema / properties / include_action_items / type
```
Removed value: -"boolean"
```

addedInput schema / properties / include_crm_matches / anyOf

Added value: +[
+  {
+    "description": "Include CRM matches",
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / include_crm_matches / description
```
Removed value: -"Include CRM matches"
```
removedInput schema / properties / include_crm_matches / type
```
Removed value: -"boolean"
```

addedInput schema / properties / recorded_by / anyOf

Added value: +[
+  {
+    "description": "Filter by recorder emails",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / recorded_by / description
```
Removed value: -"Filter by recorder emails"
```
removedInput schema / properties / recorded_by / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / recorded_by / type
```
Removed value: -"array"
```

addedInput schema / properties / teams / anyOf

Added value: +[
+  {
+    "description": "Filter by team names",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / teams / description
```
Removed value: -"Filter by team names"
```
removedInput schema / properties / teams / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / teams / type
```
Removed value: -"array"
```

Addedv1.0.0Jan 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, and description aligns with read-only retrieval. Adds value by detailing optional content inclusion (action items, CRM matches) and pagination. No contradiction.

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?

Single clear sentence followed by well-structured examples. Every element earns its place, no redundancy.

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?

Given presence of output schema, description adequately covers pagination, filtering, and optional content. Could mention sorting or ordering but not critical.

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 coverage is 100% with all parameters described. Description adds examples that illustrate usage but no new semantic information beyond schema. Baseline 3 appropriate.

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 the tool retrieves paginated meetings with filtering and optional content inclusion. It distinguishes from siblings like search_meetings and get_meeting_details by focusing on pagination and list operation.

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?

Examples provide clear usage patterns, but no explicit guidance on when to prefer this over search_meetings or other siblings. Context is clear but lacks exclusions.

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

Deploy Server