Nodes2Cloud

List runs

list_runs

Read-onlyIdempotent

List a deployed workflow's recent runs, newest first, read on demand from the user's own Cloudflare account. source: history (default) lists completed runs with an executionId, status and duration from the workflow's run log; it is empty until something has actually run. source: instances lists durable runs with an instanceId, including ones still queued, waiting or paused, and can filter by status. Pass the returned cursor back to get the next page. Open one run with get_run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflowId": "<workflowId>"
    },
    "name": "list_runs"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Runs per page, 1-100. Default 20.
`order`	No	Only with source `history`. Default newest; oldest pages through all retained history.
`cursor`	No	The cursor from the previous page, with the same source and order.
`source`	No	`history` (default): the run log. `instances`: durable runs and their state.
`status`	No	Only with source `instances`: return runs in this state.
`workflowId`	Yes	The workflow's id, from list_workflows or create_workflow.

Output Schema

Name	Required	Description	Default
`runs`	No
`cursor`	No
`source`	Yes
`nextTool`	No
`instances`	No
`truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedOct 25, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds genuine context: data is read on demand from the user's own Cloudflare account, `history` can be empty, and pagination is cursor-based. It doesn't cover rate limits or result size behavior, so it stops short of a 5.

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 default, then layered detail about sources and paging. Dense but each clause carries information; slightly packed for a single paragraph.

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?

An output schema exists so return values needn't be explained, yet the description still covers the two source modes, empty-history caveat, cursor paging, and the handoff to get_run. Nothing essential for correct invocation 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 the baseline is 3; the description adds value by explaining the default and semantics of `source`, that `status` applies only to instances, and that `order` applies only to history, plus how `cursor` is round-tripped.

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 deployed workflow's recent runs') and immediately names the two data sources with what each returns. It also distinguishes itself from the sibling get_run, which handles single-run retrieval.

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 describes when each `source` value applies, notes that `history` is empty until something has run, and routes the agent to get_run to open a single run. Alternatives and conditions are all spelled out.

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

All Nodes2Cloud tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.