Eval runs

List run iterations

Per-iteration results: actual tool calls, structured token usage, and latency. Cursor-paginated.

get/projects/{projectId}/eval-runs/{runId}/iterations

Path parameters

projectIdstring required

ID of the hosted project that contains the server.

runIdstring required

Eval run ID, as returned by POST /eval-runs.

Query parameters

limitinteger

Page size, 1–200. Defaults to 50.

cursorstring

Opaque cursor from a previous response's nextCursor.

Headers

x-mcpjam-eval-vocabulary'1' | '2'

Which vocabulary this request and its response speak. Absent means 1, which is byte-for-byte today's contract: the same request fields, the same refusals, the same response projection. 2 is the canonical vocabulary. Any other value is a 400 with code: "VALIDATION_ERROR".

Today it decides one thing: the spelling of an evaluator's policy role. Vocabulary 1 accepts and returns gating; vocabulary 2 accepts both spellings and returns the canonical required. Sending required without the header is a 400, deliberately — vocabulary 1 is not widened to meet vocabulary 2 half way, because a boundary that accepts a spelling it does not announce is one two implementations can disagree about.

A response that varies by vocabulary sends Vary: x-mcpjam-eval-vocabulary.

Response

One page of iterations.

nextCursorstring

Opaque cursor for the next page. Omitted on the last page.

Changes