crystal_recent for recent transcript context.
When to use
Use recent messages to resume a conversation or inspect what was just captured. Use search for particular wording and wake for a briefing that also includes durable context.
There is no automatic current-session restriction: pass
sessionKey. Without scope, the backend reads a bounded set of visible messages rather than every private conversation.
MCP rejects invalid limits. Raw HTTP clamps them. The stdio handler ignores nonnumeric epoch-time fields; hosted schema validation rejects wrong types. Supply numeric milliseconds or ISO date strings in their designated fields.
Raw messages remain until deletion on all tiers. Use search when wording matters more than recency.
Examples
Examples use placeholder IDs. Replace them with IDs returned by your account. MCP examples show the JSON tool arguments and the JSON inside the tool result, not the outer MCP envelope.Read the newest messages
Request:Read one session chronologically
Request:Order and scope
Chronological order makes a selected window easier to read as a conversation;newest puts the latest item first. The limit bounds the selected messages, not the entire history. Supply the session key explicitly when continuity must stay within one session.
Errors and common mistakes
Do not pass epoch seconds as milliseconds. Use ISO dates instartDate/endDate, not in numeric fields. Missing messages may be outside the selected window or visibility scope. For full redacted text rather than hosted excerpts, use raw HTTP or stdio.