Skip to main content
Glama

Workflows list

workflows_list
Read-onlyIdempotent

Lists up to 100 workspace automations with their IDs, names, purpose (why each exists, in its requester's words), enabled state, definitions and next scheduled run, plus available workflow templates. after takes nextCursor for the next page. Read only; workflows_preview inspects a proposed run without delivery, and automation_propose sets up a new automation, saved off.

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": {
      "input": "<input>"
    },
    "name": "workflows_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds behavior beyond them: a 100-item page cap, cursor-based pagination via `after`, and the fact that templates are returned alongside automations. It stops short of describing ordering or what happens past the last page.

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?

The sentence is dense and front-loaded — payload contents first, pagination second, sibling disambiguation last. It is slightly run-on with a long parenthetical about purpose, but no sentence is filler.

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?

For a paginated read with no output schema and a single functional parameter, the description covers what is returned, how paging works, and which siblings handle adjacent tasks. What remains unknown — ordering of results and template shape — is minor for a list operation.

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 coverage is 75%, and the schema already documents `after` as "Use nextCursor from the previous page." The description largely restates that, adding only the page-size limit. The `accountIds`, `userStatement` and `idempotencyKey` envelope parameters get no mention, though `idempotencyKey` is irrelevant to a read call.

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?

The description opens with a specific verb and resource ("Lists up to 100 workspace automations") and enumerates the returned fields: IDs, names, purpose, enabled state, definitions, next scheduled run, plus templates. It also explicitly separates itself from workflows_preview and automation_propose, so an agent can identify it 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?

It states the tool is read-only and names two alternatives with their distinct roles (preview inspects a proposed run without delivery; automation_propose creates and saves a new automation). That gives clear routing context, though it never says the common upstream use case — fetching an ID or cursor before invoking those siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.