Revnu

List Workflows

workflows_list

Read-onlyIdempotent

The customer's recurring workflows with their schedule, next run and steps. Read-only. In hosts that support MCP Apps, the user also sees this result in the Revnu app.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`workflows`	Yes	Non-deleted workflows, including live, paused and proposed workflows; empty when none exist.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 15, 2026
- addedOutput schema / properties / workflows / description
```
Added value: +"Non-deleted workflows, including live, paused and proposed workflows; empty when none exist."
```
- addedOutput schema / properties / workflows / items / properties / deliverTo
```
Added value: +{
+  "description": "Configured delivery destination, or null when unset.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / workflows / items / properties / description / description
```
Added value: +"The recurring growth job this workflow performs."
```
- changedOutput schema / properties / workflows / items / properties / nextRunAt / description
```
Previous value: -"Unix epoch milliseconds."New value: +"Next scheduled run as Unix epoch milliseconds, or null when not scheduled."
```
- addedOutput schema / properties / workflows / items / properties / requestedBy
```
Added value: +{
+  "description": "Label of the person who requested the workflow.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / workflows / items / properties / steps / items / properties / details / description
```
Added value: +"Instructions for performing this step."
```
- addedOutput schema / properties / workflows / items / properties / steps / items / properties / gate / description
```
Added value: +"Optional human approval gate."
```
- addedOutput schema / properties / workflows / items / properties / steps / items / properties / gate / properties / label / description
```
Added value: +"Text identifying the approval gate."
```
- addedOutput schema / properties / workflows / items / properties / steps / items / properties / gate / properties / on / description
```
Added value: +"Whether this step requires human approval."
```
- addedOutput schema / properties / workflows / items / properties / steps / items / properties / id / description
```
Added value: +"Stable step ID used by run stepResults and workflow updates."
```
- addedOutput schema / properties / workflows / items / properties / steps / items / properties / title / description
```
Added value: +"The task this step performs."
```
- addedOutput schema / properties / workflows / items / properties / url
```
Added value: +{
+  "description": "Dashboard URL for opening this workflow.",
+  "type": "string"
+}
```
- addedOutput schema / properties / workflows / items / properties / version
```
Added value: +{
+  "description": "Current workflow revision; compare with a run's workflowVersion.",
+  "type": "number"
+}
```

Changed1 schema field changedOct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "workflows": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "name": {
+            "description": "Workflow name.",
+            "type": "string"
+          },
+          "nextRunAt": {
+            "description": "Unix epoch milliseconds.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "scheduleEcho": {
+            "description": "The interpreted schedule.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "scheduleError": {
+            "description": "Why the schedule could not be interpreted.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "scheduleText": {
+            "description": "The requested recurring schedule.",
+            "type": "string"
+          },
+          "status": {
+            "description": "Current lifecycle state, including live or paused.",
+            "type": "string"
+          },
+          "steps": {
+            "description": "Complete step list; preserve unchanged steps when replacing it.",
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "details": {
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "gate": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "label": {
+                      "type": "string"
+                    },
+                    "on": {
+                      "type": "boolean"
+                    }
+                  },
+                  "required": [
+                    "on"
+                  ],
+                  "type": "object"
+                },
+                "id": {
+                  "type": "string"
+                },
+                "title": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "id",
+                "title",
+                "details"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "workflowId": {
+            "description": "Workflow ID for updates, run history and run-now calls.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "workflowId",
+          "name",
+          "status",
+          "scheduleText",
+          "steps"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "workflows"
+  ],
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so restating 'Read-only' adds nothing. The one genuinely new behavioral detail is that hosts supporting MCP Apps surface the result to the user in the Revnu app, which tells the agent the output is user-visible. That is useful but thin, so a 3 is appropriate.

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?

Three short sentences, front-loaded with what is returned before the host-behavior aside. The 'Read-only' sentence is redundant against the annotations and is the only wasted line.

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

Completeness4/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 description need not enumerate return fields, and it correctly avoids doing so while still hinting at the shape (schedule, next run, steps). Annotations carry the safety profile, so nothing critical is missing, though sibling differentiation could be stronger.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; baseline for a no-parameter tool applies. Schema coverage is reported at 100% regardless.

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

Purpose4/5

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

The description names a specific resource and enumerates its contents ('recurring workflows with their schedule, next run and steps'), so an agent knows it lists scheduled workflows rather than workflow executions. It does not explicitly name the sibling it is not (workflow_runs), but the resource framing separates them adequately.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus workflow_runs, nor any prerequisite or context trigger. Usage is only weakly implied by 'the customer's recurring workflows'. With a sibling that lists runs of those workflows, an explicit routing cue is conspicuously absent.

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

All Revnu 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?