- Category: model context protocol
- Auth: DCR_OAUTH
- Composio-managed OAuth available? No
- Tools: 4
- Triggers: 0
- Slug:
READ_AI_MCP - Version: 20261018_00
Tools
Create meeting agent
Create meeting agent
Slug:
READ_AI_MCP_CREATE_MEETING_AGENTSend a Read AI meeting agent (bot) to a video conferencing meeting on behalf of the authenticated user. This creates a new Read AI meeting ID and the agent will attempt to join the meeting to record & transcribe it for the user.When to call this tool
Call this tool when:- The user explicitly asks for an agent to “join”, “record”, “capture,” “send a bot to”, or “take notes on” a specific meeting they identify on their calendar, by providing a meeting link, or specifying a video conferencing platform with a meeting ID and optional password.
- The meeting is on a supported platform (Zoom, Google Meet, Microsoft Teams)
- For meetings the user has not explicitly authorized an agent to join.
- To join arbitrary or guessed meeting IDs.
- If a user wants to record using a desktop or mobile client. Those are available from Read AI’s website (https://read.ai) and can be used separately.
Parameters
meeting_url : str Meeting URL that can be used to join the meeting. If provided, the meeting_platform and meeting_id will be extracted from the URL and those additional parameters are not required.meeting_platform : str The video conferencing platform for the meeting. Must be one of:- “zoom” (Zoom)
- “meet” (Google Meet)
- “teams” (Microsoft Teams)
Returns
str The ULID for the newly created (or matched existing) Read AI meeting that the the meeting recording agent has been dispatched for. This meeting ID can be passed to other tools such asget_meeting_by_id once the meeting has progressed far enough to have data available.Behavior and edge cases
- Authentication:
- Access token is handled internally; do not supply user IDs or tokens.
- If missing or invalid, the tool fails with errors such as:
- “Unauthorized: No access token provided”
- “Invalid token: No subject in access token claims”.
- Validation:
meeting_idis required and must be non-empty if a meeting_url is not provided.- If the platform / meeting combination is unsupported or the agent cannot be deployed (e.g. mobile/desktop platforms, or missing required platform integrations), the tool will fail with an error.
- Idempotency:
- This tool is idempotent. If an entry for the same meeting already exists in an active state, the system may return the existing meeting ID instead of creating a new one.
- Side effects:
- An agent may join the live meeting and a new meeting ID is created in Read AI.
Usage examples for agents
- User: “Have Read AI record my Zoom meeting 1234567890.” -> Call: { “meeting_platform”: “zoom”, “meeting_id”: “1234567890” }
- User: “Send the Read AI bot to my Google Meet abc-defg-hij.” -> Call: { “meeting_platform”: “meet”, “meeting_id”: “abc-defg-hij” }
- User: “Join my Zoom 9876543210 with passcode hunter2.” -> Call: { “meeting_platform”: “zoom”, “meeting_id”: “9876543210”, “meeting_password”: “hunter2” }
- User: “Join my meeting now: https://meet.google.com/abc-defg-hij” -> Call: { “meeting_url”: “https://meet.google.com/abc-defg-hij” }
- User: “Join my meeting at 2026-05-21T15:00:00Z: https://meet.google.com/abc-defg-hij” -> Call: { “meeting_url”: “https://meet.google.com/abc-defg-hij”, “start_time”: “2026-05-21T15:00:00Z” }
- User: “Join my Zoom 1234567890 and call it ‘Q3 Planning Sync’.” -> Call: { “meeting_platform”: “zoom”, “meeting_id”: “1234567890”, “title”: “Q3 Planning Sync” }
Input Parameters
Optional title to stamp on the created meeting. If omitted, the meeting is given a generic platform-derived default (e.g. ‘Zoom Meeting’).
The platform-specific meeting identifier (e.g. a Zoom meeting number or Google Meet code). Required unless meeting_url is provided, in which case the id is parsed from the URL.
Optional start time to stamp on the created session. Use ISO 8601 format, e.g. ‘2026-05-21T15:00:00’ or ‘2026-05-21T15:00:00Z’. If omitted, the session is stamped with the current time at creation.
Optional full meeting URL (e.g. a Zoom join link or Google Meet URL). When provided, meeting_platform, meeting_id, and meeting_password are derived from the URL and need not be supplied separately.
The video meeting platform (e.g. ‘zoom’, ‘meet’, ‘teams’). Required unless meeting_url is provided, in which case the platform is inferred from the URL.
Output
Get meeting by
Get meeting by
Slug:
READ_AI_MCP_GET_MEETING_BY_IDRetrieve a single Read AI meeting (owned by or shared with the authenticated user) by its ULID identifier, with optional expansion of rich meeting content.When to call this tool
Call this tool only when:- You already have a specific meeting ID (a ULID), and
- The user wants information about that one meeting, such as:
- Metadata (title, times, participants, platform, report URL)
- Summary / chapter summaries
- Action items / key questions
- Topics discussed
- Full transcript
- Metrics/analytics
- A link to download the recording
- To search or browse meetings by title, date, participant, or keywords (use a dedicated list/search tool instead).
- When working with multiple meetings at once.
- With guessed or fabricated IDs. Only use IDs explicitly provided by the user or returned from another tool.
Parameters
id : str The Read AI meeting identifier in ULID format.- 26-character, case-insensitive, base32 ULID string (e.g. “01KA3883FYZSFZXE391Q0FMV39”).
- Must come from:
- A previous tool (e.g., a meeting list/search tool), or
- Explicit user input.
- Do not invent, modify, or “fix” IDs.
None. Request the smallest set that satisfies the user’s need. Each additional expand value can increase latency and resource usage, especially “transcript”.Allowed values (strings):- “summary”: concise natural-language overview of the meeting.
- “chapter_summaries”: breakdown into labeled sections/chapters.
- “action_items”: follow-up tasks and next steps.
- “key_questions”: important or open questions discussed.
- “topics”: main themes/subjects covered.
- “transcript”: detailed spoken content of the meeting, including who spoke and what they said, suitable for verbatim quotes and fine‑grained analysis.
- “metrics”: high-level analytics (e.g., read_score, sentiment, engagement).
- “recording_download”: url to download the meeting recording.
Output
MeetingEvent A single meeting object with:- Base metadata (id, title, start/end times, scheduled times, platform, platform_id, report_url, folders).
access_level: the authenticated caller’s access level on this meeting, one of “owner”, “editor”, “viewer_full”, or “viewer_recap_only” (or null if it could not be resolved). “editor” or “owner” is required to share the report via theshare_meeting_reporttool.- Owner and participants (with name/email and attendance status).
- Expandable fields populated only if requested in
expand:summary: Optional[str]chapter_summaries: Optional[List[Chapter]]action_items: Optional[List[str]]key_questions: Optional[List[str]]topics: Optional[List[str]]transcript: Optional[Transcript]metrics: Optional[Metrics]recording_download: Optional[RecordingDownload]
Behavior and edge cases
- Authentication:
- Access token is handled internally; do not supply it as a parameter.
- If missing or invalid, the tool fails with errors such as:
- “Unauthorized: No access token provided”
- “Invalid token: No subject in access token claims”.
- Not found / access issues:
- If the ID is invalid or the meeting is not accessible to the user, the tool fails with “Not Found”.
- If the user’s Read AI account does not have sufficient quota to view the meeting, the tool fails with an “Out of quota” error. This is a billing issue and the user can resolve it by upgrading their plan. They can resolve this by visiting “https://app.read.ai/analytics/meetings/{meeting_id}” in their browser, where {meeting_id} is the provided meeting ID.
- Idempotency:
- Read-only and idempotent. Calling with the same arguments returns the same logical result.
Usage examples for agents
- User: “Give me the summary and action items from meeting 01H9T5X9G5K3M7Y8R0D8AYZ5WQ.” -> Call: { “id”: “01H9T5X9G5K3M7Y8R0D8AYZ5WQ”, “expand”: [“summary”, “action_items”] }
- User: “Who said ‘We should move this to next quarter’ in meeting <meeting_ulid>?” -> You need detailed speech text: { “id”: “<meeting_ulid>”, “expand”: [“transcript”] }
Input Parameters
Output
List meetings
List meetings
Slug:
READ_AI_MCP_LIST_MEETINGSList Read AI meetings for the authenticated user with optional start-time filters and cursor-based pagination.When to call this tool
Call this tool when:- You need to browse or filter a user’s meetings by time range.
- You need meeting IDs (ULIDs) that can later be used with a “get_meeting_by_id” tool for detailed inspection.
- You want a page of recent meetings (optionally with summaries or metrics).
- When you already know the specific meeting ID and only need that single meeting (use the “get_meeting_by_id” tool instead).
- To search by title, participant, or arbitrary keywords (use a search tool if available).
- To guess or fabricate meeting IDs.
Parameters
limit : int, default 10 (max 10) Maximum number of meetings to return in this page.- Must be ≤ 10.
- If omitted, defaults to 10.
- Typically use either
start_datetime_gtorstart_datetime_gte, not both.
- Typically use either
start_datetime_ltorstart_datetime_lte, not both. - For a closed interval [A, B], use:
start_datetime_gte = Astart_datetime_lte = B
- First page: omit or pass
null. - Next page: pass the ID of the last meeting returned in the previous page (
previous_response.data[-1].id), which acts as a “start after this” pointer.
None. Because this is a list endpoint, expansions apply to every meeting in the page and can be expensive. Request only what the user needs.Allowed values (strings), with the same meanings as in get_meeting_by_id:- “summary”: concise overview of each meeting.
- “chapter_summaries”: section/chapter breakdown.
- “action_items”: follow-up tasks per meeting.
- “key_questions”: important or open questions per meeting.
- “topics”: main themes/subjects per meeting.
- “transcript”: full spoken content per meeting.
- “metrics”: analytics such as read_score, sentiment, engagement.
- “recording_download”: url to download the meeting recording.
Returns
ListMeetingResponse A paginated list of meetings with:object: str – always “list”.url: str – API-style URL for this collection.has_more: bool – True if there are more meetings beyond this page.data: List[MeetingEvent] – meetings matching the filters, each with:- Core metadata (id, title, start/end times, platform, etc.).
access_level: the caller’s access level on the meeting (“owner”, “editor”, “viewer_full”, “viewer_recap_only”, or null). “editor”/“owner” is required to share the report viashare_meeting_report.- Owner and participants.
- Any expandable fields populated according to
expand.
Behavior and edge cases
- Authentication:
- Access token is handled internally; do not pass it as a parameter.
- If missing or invalid, the tool raises errors such as:
- “Unauthorized: No access token provided”
- “Invalid token: No subject in access token claims”.
- Filtering:
- All provided filters are combined with logical AND.
- Conflicting ranges (e.g., lower bound after upper bound) will typically return an empty result.
- Prefer at most one lower-bound parameter (
gtorgte) and one upper- bound parameter (ltorlte).
- Pagination:
limitcontrols the number of meetings per page (max 10).- Use
has_morepluscursor(last meeting’s id fromdata) to fetch subsequent pages.
- Idempotency:
- Read-only and idempotent. Repeating the same call yields the same logical results, except for new meetings created in the underlying system.
Usage examples for agents
- Get the 10 most recent meetings (no filters, first page): -> Call: { “limit”: 10 }
- Get meetings in November 2025, including brief summaries: -> Call: { “limit”: 10, “start_datetime_gte”: “2025-11-01T00:00:00”, “start_datetime_lte”: “2025-11-30T23:59:59”, “expand”: [“summary”] }
- Page through all recent meetings since 2025-11-01: First page: -> Call: { “limit”: 10, “start_datetime_gte”: “2025-11-01T00:00:00” } Next page (if has_more is true): -> Call: { “limit”: 10, “start_datetime_gte”: “2025-11-01T00:00:00”, “cursor”: “<id_of_last_meeting_from_previous_page>” }
- Find candidate meetings to inspect in detail later:
- First, list meetings with summaries and metrics: { “limit”: 5, “expand”: [“summary”, “metrics”] }
- Then, pick a specific meeting ID and call
readai_get_meeting_by_idwithexpand=["transcript"]if you need the full conversation.
Input Parameters
Cursor for the next page. For the first page, omit this. For subsequent pages, set this to the ID (ULID) of the last meeting (
data[-1].id) returned in the previous response.Only return meetings with start times strictly after this datetime (exclusive lower bound). Use ISO 8601 format, e.g. ‘2025-11-01T00:00:00’ or ‘2025-11-01T00:00:00Z’.
Only return meetings with start times strictly before this datetime (exclusive upper bound). Use ISO 8601 format, e.g. ‘2025-11-01T23:59:59’
Only return meetings with start times on or after this datetime (inclusive lower bound). Use ISO 8601 format, e.g. ‘2025-11-01T00:00:00’