Tessryx

List workflow runs

list_runs

Read-onlyIdempotent

List a workflow's past runs, most-recent-first, by workflow id; or, with chain_id, one chain's runs in link order (a chain is a long job run as successive runs of one workflow; its id is the run_id of its first run). Optionally filter by status (succeeded, failed, running, cancelled). Returns run summaries (run_id, status, message, timestamps, and chain for a run in a chain: its link_index and whether it continues, false once the chain has finished); use get_workflow_run for a run's output or get_workflow_run_traces for per-step detail.

Input Schema

TableJSON Schema

Name	Required	Description
`status`	No	optional status filter: succeeded, failed, running, or cancelled; omit for all
`chain_id`	No	list one chain's runs instead, in link order: the chain id is the run_id of its first run
`page_size`	No	maximum number of runs to return in this page
`page_token`	No	token from a previous response's next_page_token to fetch the next page
`workflow_id`	No	the workflow id whose runs to list (most recent first); required unless chain_id is given

Output Schema

TableJSON Schema

Name	Required	Description	Default
`runs`	Yes
`next_page_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 15, 2026

addedInput schema / properties / chain_id

Added value: +{
+  "description": "list one chain's runs instead, in link order: the chain id is the run_id of its first run",
+  "type": "string"
+}

changedInput schema / properties / workflow_id / description

Previous value: -"the workflow id whose runs to list"New value: +"the workflow id whose runs to list (most recent first); required unless chain_id is given"

removedInput schema / required
```
Removed value: -[
-  "workflow_id"
-]
```

addedOutput schema / properties / runs / items / properties / chain

Added value: +{
+  "additionalProperties": false,
+  "description": "present only for a run that is part of a chain",
+  "properties": {
+    "chain_id": {
+      "description": "the chain's id: the run_id of its first run",
+      "type": "string"
+    },
+    "continues": {
+      "description": "true if another run of the chain was queued after this one; false on the last run, when the chain has finished",
+      "type": "boolean"
+    },
+    "link_index": {
+      "description": "this run's place in the chain, 0 for the first",
+      "maximum": 2147483647,
+      "minimum": -2147483648,
+      "type": "integer"
+    },
+    "origin": {
+      "description": "what started the chain when it was not a schedule: mcp, schedule_manual",
+      "type": "string"
+    }
+  },
+  "required": [
+    "chain_id",
+    "link_index",
+    "continues"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

First observedSep 7, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare a safe read (readOnly, idempotent, non-destructive), and the description adds substantial behavioral context beyond them: most-recent-first ordering, link-order for chains, the meaning of chain termination ('false once the chain has finished'), and the fields returned per run.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and dense with useful distinctions, though the enumeration of return fields is somewhat redundant given the output schema and the description reads as one long run-on sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with full schema coverage, an output schema, and safe-read annotations, the description covers ordering, chaining semantics, filtering, and sibling routing. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already documented, but the description adds real meaning: it defines a 'chain' as successive runs of one workflow and explains that a chain_id is the run_id of its first run, plus the allowed status values, going beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List a workflow's past runs') and covers both operating modes (by workflow_id, or by chain_id). Names sibling tools (get_workflow_run, get_workflow_run_traces) so the agent can distinguish it from adjacent list/get operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use this to list runs, but use get_workflow_run for a run's output and get_workflow_run_traces for per-step detail. It also specifies the optional status filter and when to omit it, leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tessryx tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?