List a project's runs
list_runsList a project's runs, newest first, with each run's id, status, trigger, pages read and pages changed. Use it to find a run_id for list_pages or get_changes, to check whether a run is still going before start_run, or to find the run to stop with cancel_job. get_project shows only the last run. Inputs: project_id from list_projects. limit=5 finds the latest few; runs past the limit cannot be paged. Errors: an unknown project answers 404. Read-only and free: it reads stored data and never fetches.
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": {
"project_id": "<project_id>"
},
"name": "list_runs"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many runs to return, 1 to 100 (default 25). | |
| project_id | Yes | The project's 32-character hex id, from list_projects. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Only on a failure: a machine-readable reason, e.g. read_only, validation, plan_limit or not_found. | |
| runs | No | Each {id, status, trigger, scope, pages, changed, errors, counts, coverage, stop, startedAt, elapsed, baseline, rebaselined}; baseline is a first run with nothing to compare, rebaselined one whose settings changed how pages read, so it was recorded rather than compared. | |
| error | No | Only when the call failed: what went wrong, in words an assistant can act on. | |
| detail | No | Only on a failure: the API's own wording, when the error was rephrased. | |
| status | No | Only on a failure: the HTTP status code. |