---
title: "Get an iteration's step results"
method: GET
path: "/projects/{projectId}/eval-runs/{runId}/iterations/{iterationId}/steps"
tags: ["Eval runs"]
---

# Get an iteration's step results

`GET /projects/{projectId}/eval-runs/{runId}/iterations/{iterationId}/steps`

One row per authored test step, in order, with `status` (`ok`/`fail`/`skipped`/`pending`), a `reason`, and any `evidence` (screenshots, replay-video offset, widget tool calls). The fastest way to see which step failed and why. Unlike `/trace`, a missing trace is not a `404` — step verdicts still return, just without evidence.

## Path parameters

- `projectId` string, required
- `runId` string, required
- `iterationId` string, required

## Response `200`

The ordered step results as a page envelope.

- object
  - `items` object[], required — Authored steps in order with their verdict.
    - `stepId` string, required
    - `stepIndex` integer, required
    - `kind` 'prompt' | 'toolCall' | 'interact' | 'assert', required
    - `status` 'ok' | 'fail' | 'skipped' | 'pending', required
    - `reason` string, nullable
    - `evidence` object — Optional, omitted when the step produced none.
  - `nextCursor` string

## Other responses

- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.

---

[API](https://skmtc.net/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.net/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/revisions/b767df188d0c/schema)