> ## 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.

# Get a measurement run

> Read execution status, data-family readiness, and available run counts.

Read execution status, data-family readiness, and available run counts.

**MCP tool:** `get_run`. **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. |
| `run_id` | string | Yes | `Required` | Run ID from list\_runs for this project. Use the exact returned value and check readiness before reading measurements. |

## 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": "get_run",
  "arguments": {
    "project_id": "PROJECT_ID",
    "run_id": "RUN_ID"
  }
}
```

## Read the response

Top-level fields include `status`, `data_ready`, `data_readiness`, and available count fields. Some counts are null. `results_stability` and `results_stability_detail` are not populated here.

### 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 |
| - | - |
| `status` | Execution state for this run. |
| `data_ready` | Summary data readiness; separate from statistical stability. |
| `completed_at` | Measurement completion timestamp. |
| `n_queries_submitted` | Submitted query count, not the number of returned answer statements. |
| `n_responses_pipeline` | Unpopulated in this edition. Preserve null as unavailable rather than reporting zero responses. |
| `results_stability` | Unpopulated in this endpoint. Request get\_results\_stability for quality assessment. |

## 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}
{
  "run_id": "RUN_ID",
  "status": "COMPLETED",
  "data_ready": true,
  "completed_at": "2026-09-24T18:23:55.508870+00:00",
  "n_queries_submitted": 240,
  "n_responses_pipeline": null,
  "results_stability": null
}
```

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

## Important behavior

Use a UUID returned by discovery. Request `get_results_stability` separately; do not use a null count as zero.

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: [Get a measurement run](/developers/http/http-get-run). HTTP parameters and defaults can differ.


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