get_messages
Retrieve up to 100 messages and transcripts by ID in one call, in the given order. Use when you have multiple message IDs and need their content without fetching each separately.
Instructions
Get up to 100 messages by ID in one call, in the order given.
USE WHEN: You already have several message IDs (from search_transcripts, search_message_ids, an AI action) and need their transcripts. One call instead of one get_message per ID.
USE INSTEAD: get_message for one ID or to expand conversation/creator/labels; list_messages to browse a conversation without IDs.
FIRST: message_ids comes from search_transcripts (field results[].message_id, or workspaces[].results[].message_id) — call it first if you don't have one.
EXAMPLE: {"message_ids":["msg-abc","msg-def"]}
RETURNS: By default {results: [{id, conversation_id, creator_id, created_at, status, content.transcript, content.ai_summary}], missing_ids}; response_fields: ["results"] for whole messages (content.time_codes has one entry per word). status not active (e.g. processing): not ready, call again later. missing_ids: not found, no access, or deleted; do not retry them.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| language | No | Language of transcript and summary (e.g. `es`). Original when omitted. | |
| message_ids | Yes | Message ids to fetch, 1-100. Results keep this order. | |
| response_fields | No | Dot-path allowlist. Omit for the default fields in RETURNS; ["results"] for whole messages. |