Croncool Cron Jobs

List workflow runs

list_workflow_runs

Read-onlyIdempotent

Use this when the user wants to list executions of a durable workflow in CronCool, with optional workflow-name and status filters. Returns each run's id, workflow name, status, timings and error code, newest first by default, 20 per page with a cursor, filterable by workflow and status. Not for one run's steps.

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": {
      "projectId": "<projectId>"
    },
    "name": "list_workflow_runs"
  }
}

Input Schema

Name	Required	Description
`sort`	No	newest (default) or oldest first
`limit`	No	Runs per page, from 1 to 100; defaults to 20
`cursor`	No	The nextCursor of the previous page with the same project, workflow, status and sort; absent for the first page
`status`	No	Only runs in this status: pending, running, completed, failed or cancelled
`projectId`	Yes	Project id
`workflowName`	No	Only runs of this workflow name

Output Schema

Name	Required	Description
`runs`	Yes	Run identity, status, timings and machine error code. Workflow inputs, outputs and error messages are excluded.
`hasMore`	Yes
`nextCursor`	Yes	Cursor for the next page with the same filters; null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 27, 2026

changedInput schema / properties / cursor / description

Previous value: -"Opaque nextCursor from an earlier call with the same project, workflow, status, and sort filters"New value: +"The nextCursor of the previous page with the same project, workflow, status and sort; absent for the first page"

changedInput schema / properties / limit / description

Previous value: -"Maximum number of runs to return (default 20, max 100)"New value: +"Runs per page, from 1 to 100; defaults to 20"

changedInput schema / properties / projectId / description

Previous value: -"Project id whose workflow runs should be listed (required)"New value: +"Project id"

changedInput schema / properties / sort / description

Previous value: -"Order of the returned runs (default newest first)"New value: +"newest (default) or oldest first"

changedInput schema / properties / status / description

Previous value: -"Only return runs in this status"New value: +"Only runs in this status: pending, running, completed, failed or cancelled"

changedInput schema / properties / workflowName / description

Previous value: -"Only return runs of this workflow"New value: +"Only runs of this workflow name"

addedOutput schema / properties / nextCursor / description

Added value: +"Cursor for the next page with the same filters; null on the last page"

addedOutput schema / properties / runs / description

Added value: +"Run identity, status, timings and machine error code. Workflow inputs, outputs and error messages are excluded."

First observedSep 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: return fields, newest-first default ordering, 20-per-page pagination with a cursor, and filterability.

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?

Two tight sentences with the usage trigger front-loaded and the exclusion placed last. Minor redundancy: the workflow/status filtering is stated twice, which slightly dilutes the efficiency.

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?

With an output schema present, the return-shape sentence is a bonus rather than a necessity. All an agent needs to invoke this list tool correctly – trigger, scope, filters, ordering, paging, exclusion – is present.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all six parameters including enums, limits and cursor semantics. The description paraphrases the filter and paging behavior but adds no format or syntax detail beyond what the schema provides, making the baseline 3 correct.

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+resource ('list executions of a durable workflow') and immediately scopes it against the sibling get_workflow_run with 'Not for one run's steps.' An agent can distinguish it from get_workflow_run and get_job_runs without opening any schema.

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

Usage Guidelines4/5

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

Opens with an explicit when-to-use trigger ('when the user wants to list executions...') and includes an exclusion ('Not for one run's steps'). It stops short of naming the sibling to use instead, so the routing is clear but not fully closed.

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

All Croncool Cron Jobs 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?