> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iqrush.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# List measurement runs

> Find measurement runs for a project, newest first.

Find measurement runs for a project, newest first.

**MCP tool:** `list_runs`. **Operation:** read. Uses the authorized connection; no project or content changes are made by this tool.

## Parameters

| Name | Type | Required | Default | Meaning and accepted values |
| - | - | - | - | - |
| `project_id` | string | Yes | `Required` | Project ID from list\_projects. Select the project in the intended workspace and environment. |

## Example call

Replace ID placeholders and example selections with values from your account. This is the `params` object for MCP `tools/call`.

```json theme={null}
{
  "name": "list_runs",
  "arguments": {
    "project_id": "PROJECT_ID"
  }
}
```

## Read the response

Top-level `runs` contains `run_id`, execution timestamps, `status`, `data_ready`, and `cold_path_ready` when known. `count` counts the returned runs.

### Fields to use

These selected fields explain the example and the result to preserve. Field presence depends on the response; this is not a complete response schema.

| Field | Meaning and use |
| - | - |
| `runs[].run_id` | ID to retain for all reads of the chosen measurement. |
| `runs[].status` | Execution state. Select a COMPLETED run for a finished measurement. |
| `runs[].completed_at` | Completion timestamp; use this as the measurement date rather than the response-generation time. |
| `runs[].data_ready` | Whether the run’s summary data is ready. |
| `runs[].cold_path_ready` | Whether the data used for grouped and filtered reads is ready. False can explain a temporary empty result. |
| `count` | Number of returned runs in the full response; the example list is shortened. |

## Response example

Selected fields from an observed IQRush Dev response. Lists are shortened and project/run IDs are placeholders. Omitted fields remain available in the actual response.

```json theme={null}
{
  "project_id": "PROJECT_ID",
  "runs": [
    {
      "run_id": "RUN_ID",
      "status": "COMPLETED",
      "completed_at": "2026-09-24T18:23:55.508870+00:00",
      "data_ready": true,
      "cold_path_ready": true
    }
  ],
  "count": 2
}
```

Read the actual returned scope, counts, and interval levels before interpreting these fields.

## Important behavior

Execution completion, summary readiness, grouped-data readiness, and convergence are different checks.

Check tool and payload errors before using the result. [Response handling](/developers/guides/09-responses-and-metrics) explains estimates and empty results; [errors and recovery](/developers/guides/13-errors) covers invalid requests and temporary failures.

HTTP equivalent: [List measurement runs](/developers/http/http-list-runs). HTTP parameters and defaults can differ.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.