get_run_output
Retrieve a single named output from a completed model run. Use this instead of get_run when you only need one output and want to avoid the get_run inline cap for large multi-tab runs. Resolves run_id using full UUID or UUID prefix. Requires a successful run status.
read-only · idempotent
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
run_id | Annotated[str, Field(description='UUID of a completed model run, or a short UUID prefix. Use list_runs to discover run IDs.')] | Yes | — | |
output_name | Annotated[str, Field(description="Key in the run's outputs dict to retrieve (e.g. 'forecast.json' or 'revenue').")] | Yes | — | |
encoding | Annotated[Literal['auto', 'json', 'text', 'base64'], Field(description="How to encode the returned content: 'auto' (default) sniffs content type; 'json' returns raw JSON; 'text' returns text; 'base64' returns base64-encoded bytes.")] | No | 'auto' |
Returns
Section titled “Returns”Returns a structured object. Top-level fields:
run_id(string)project_name(string)output_name(string)resolved_output_name(string)content(array<object>)encoding(string)size_bytes(integer)truncated(boolean)resolution_path(string)
See the response example below for the full payload shape.
Example
Section titled “Example”Tool Call
Section titled “Tool Call”{ "name": "get_run_output", "arguments": { "run_id": "66666666-6666-6666-6666-666666666666", "output_name": "revenue", "encoding": "auto" }}Response
Section titled “Response”{ "run_id": "66666666-6666-6666-6666-666666666666", "project_name": "forecasts", "output_name": "revenue", "resolved_output_name": "revenue", "content": [ { "month": "2026-01", "revenue": 100 }, { "month": "2026-02", "revenue": 110 } ], "encoding": "json", "size_bytes": 78, "truncated": false, "resolution_path": "literal"}- Module:
Execution - Requires authentication via API token or Auth0 JWT.