Atwork

List Workflows

workflow.list

Read-onlyIdempotent

List workflows, optionally for one sheet, with their state: on or off, published version, unpublished draft changes. deleted: true lists deleted ones for workflow.restore; templates: true lists the built-in templates for workflow.from_template.

Input Schema

Name	Required	Description
`deleted`	No	List deleted workflows instead, to bring one back with workflow.restore
`sheetId`	No	Only the workflows of this sheet
`templates`	No	List the built-in templates for workflow.from_template instead

Output Schema

Name	Required	Description	Default
`templates`	No
`workflows`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026
- removedOutput schema / properties / workflows / items / properties / trigger / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / workflows / items / properties / trigger / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedOct 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect profile are covered. The description adds useful behavior beyond that: what fields each listed workflow carries (on/off state, published version, unpublished draft changes) and the two alternate result sets. It omits anything about result size or ordering, which is the only meaningful gap.

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

Conciseness5/5

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

Two compact clauses, no filler, with the primary behavior front-loaded before the two flag-specific modes. Every element (state fields, sheet scoping, both flags) earns its place.

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?

All three optional parameters are covered, an output schema exists so return values need not be described, and the description still names the payload fields an agent will act on. Nothing needed to invoke it correctly is missing.

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 all three parameters are already documented in structured form. The description mostly restates the flag semantics and adds only a light pointer to the consuming tool (workflow.restore, workflow.from_template); it adds no format or interaction detail (e.g. whether deleted and templates can be combined). Baseline 3 applies.

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 workflows') and immediately scopes it ('optionally for one sheet') while enumerating exactly what comes back (state on/off, published version, unpublished draft changes). The two flag modes are tied to the sibling tools they serve, so an agent can distinguish this from workflow.read or workflow.restore without opening a 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?

Explicitly states the conditions that select the two non-default modes: `deleted: true` is for bringing one back via workflow.restore and `templates: true` is the feed for workflow.from_template. It does not spell out the default case (live, non-deleted workflows) or contrast with workflow.read for a single workflow, leaving a small inference gap.

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

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