[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# List calls

> Calls from My Calls or Team Calls, newest first, with title, date, meeting type and open action items. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/fathom-video/list_calls

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Calls from My Calls or Team Calls, newest first, with title, date, meeting type and open action items.

Fathom MCP tools: https://cotlet.dev/docs/mcp/fathom-video.md

MCP tool: `fathom_video_read → list_calls`

Access: read.

Lists calls the way the My Calls and Team Calls pages show them, newest first; pass next_cursor back as cursor for the next page. scope team_calls works for accounts on a Team plan. meeting_type filters by one of your Meeting Types, and created_after and created_before bound the date. open_action_items counts the items on the call that are not completed. Use call_id with the other tools.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `scope` | enum | no | my_calls (default) or team_calls. |
| `created_after` | date | no | Only calls recorded on or after this date. |
| `created_before` | date | no | Only calls recorded before this date. |
| `meeting_type` | string | no | Name of a Meeting Type, as shown on the call. |
| `cursor` | string | no | Next page cursor from the previous call. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "fathom_video_read",
    "arguments": {
      "operation": "list_calls",
      "arguments": {}
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "calls": [
      {
        "call_id": "610313346",
        "title": "Q4 pricing review",
        "recorded_at": "2026-10-21T15:00:00Z",
        "meeting_type": "External",
        "attendees": 4,
        "open_action_items": 3,
        "url": "https://fathom.video/calls/610313346"
      },
      {
        "call_id": "610298114",
        "title": "Vendor onboarding sync",
        "recorded_at": "2026-10-20T09:30:00Z",
        "meeting_type": "External",
        "attendees": 3,
        "open_action_items": 1,
        "url": "https://fathom.video/calls/610298114"
      }
    ],
    "next_cursor": "c_2"
  },
  "isError": false
}
```

Next: [Get a call](https://cotlet.dev/docs/mcp/fathom-video/get_call.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.