get_v1_agents_ref_runs
ListAgentRuns returns one agent's execution history, newest first — each run's input, its output or its error, and how long it took.
ListAgentRuns returns one agent's execution history, newest first — each run's input, its output or its error, and how long it took. Every row is a run that actually happened.
| Tool | get_v1_agents_ref_runs |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | GET /v1/agents/{ref}/runs |
| Product | agents |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
limit | integer | — | — | — | Limit caps how many runs come back, newest first. Absent, zero or out of range (1..200) reads as 50. |
ref | string | yes | — | — | Ref is the agent's public id or its org-unique name, from the path. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from GET /v1/agents/{ref}/runs, the operation this tool dispatches to — the same declaration the REST API validates against. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_v1_agents_ref_runs",
"arguments": {
"ref": "<ref>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_get_v1_agents_ref_runs | GET /v1/agents/{ref}/runs | agents | ListAgentRuns returns one agent's execution history, newest first — each run's input, its… |
The same capability over plain HTTP is in the agents API reference, on https://api.hanzo.ai.
All 833 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?