next_page
Read the next rows from a query cursor when run_query stops at max_rows or max_bytes, returning another page without rerunning the statement.
Instructions
Reads the next rows of a result that run_query cut at max_rows or max_bytes, from the cursor it returned, instead of running the statement again: the pages come from the rows read with the first one (up to 10000 more rows, 4 MB or 250 ms of reading; the answer says when the result has more than that), so they do not change if the data does. Same format, max_rows (default 100) and max_bytes as run_query, with the connection's limits and calls per minute; sensitive columns stay masked as in the first page. A cursor is kept 5 minutes after its last use and belongs to this session; an unknown, expired or another session's cursor is refused.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"cursor": "<cursor>"
},
"name": "next_page"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | Yes | The `cursor` a `run_query` or an earlier `next_page` returned. | |
| format | No | `text` (an aligned table, the default) or `json`. | |
| max_rows | No | Rows returned at most (default 100, up to 10000). | |
| max_bytes | No | Bytes of output at most (default 32768, up to 1048576). |