get_chat
Retrieve a full conversation by its UUID, with pagination support to load long chats in parts.
Instructions
Fetch a specific conversation from history by uuid (with pagination).
USE when:
You have already identified a relevant chat (usually via
search_chats) and need more context than the result snippet.The user gave you a specific uuid and asked you to review it.
You are following a thread and need detail from a specific chat that appeared earlier in the conversation.
DO NOT use to discover new chats without searching first. To find
chats by topic or keyword, use search_chats.
If the chat is long, call again with messages_offset to paginate
(truncated response is indicated by truncated: true and
total_messages).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | Chat UUID (typically obtained via `search_chats` or `list_recent_chats`). | |
| messages_limit | No | How many messages to fetch starting from the offset (default 10, max 100). Individual messages are truncated to 1500 chars so the total response fits in the MCP client's token cap (~17k chars worst case with the default). If you need more detail per message, ask for fewer messages (e.g. messages_limit=5) and you can request a higher messages_limit in chats with short messages. | |
| messages_offset | No | How many messages to skip from the start of the chat (default 0). Use this to paginate long chats: first call with offset=0, second with offset=10, etc. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |