Skip to content

support_message_list

List messages oldest first — the conversation reads forward.

Tool

support_message_list

List messages oldest first — the conversation reads forward.

List messages oldest first — the conversation reads forward. Name a threadId to read one thread, or omit it to read every thread of this product, which is how a client catches up on what it missed: pass since with the timestamp of the last message it has, then follow nextCursor until it comes back null. Paging is stable across messages that share a timestamp, so a walk neither skips nor repeats one. Filter by direction and by visibility; omit visibility to get public messages and internal notes together. A thread belonging to another product is reported as not found

Behavior

HTTP
GET /support/messages

Arguments

Name
Type
Required
Description
limit
integer
—
Page size, 1..100 (default 50)
since
string
—
ISO-8601 timestamp. Only messages created strictly after it — pass the createdAt of the last message you already have
cursor
string
—
Opaque position from a previous nextCursor. Resumes exactly where that page ended, with no gap and no repeat even when messages share a timestamp. Never construct one, and do not combine it with offset
offset
integer
—
Number of messages to skip. The older pagination, kept for callers that already use it; prefer cursor, which cannot drift as messages arrive
threadId
string
—
Thread whose messages to list. Omit to list the messages of every thread of this product — the catch-up read
direction
string
—
Only messages in this direction
visibility
string
—
Only messages with this visibility. Omit to get both public and internal

Response

Field
Type
Always
Description
limit
integer
•
Page size that was applied
offset
integer
•
Offset that was applied
messages
array
•
The requested page of messages, oldest first — the conversation reads forward
nextCursor
string
•
Position to resume from: pass it back as cursor for the next page. Null when this page is the last one

Try it

List messages oldest first — the conversation reads forward.

When to use

List messages oldest first — the conversation reads forward. Name a threadId to read one thread, or omit it to read every thread of this product, which is how a client catches up on what it missed: pass since with the timestamp of the last message it has, then follow nextCursor until it comes back null. Paging is stable across messages that share a timestamp, so a walk neither skips nor repeats one. Filter by direction and by visibility; omit visibility to get public messages and internal notes together. A thread belonging to another product is reported as not found

Example

Ask your agent something like this:

List messages oldest first — the conversation reads forward.

The agent will invoke support_message_list with these arguments:

{}

Esc

Start typing to search the docs.

↑↓navigate↵select