Skip to main content
Glama

List workflows

list_workflows
Read-only

Ready-made workflows (e.g. text-to-clip, product-to-ad, effect presets): multi-step pipelines built on the capabilities. Each has an inputs form (name -> type, label, required, default, options for choices), its outputs, the steps it runs, available with unavailable_reasons, and credits_estimate at default settings. Prefer a workflow over chaining generate calls by hand when one fits. Filter by category (image, video, audio).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_workflows"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds a genuinely useful behavioral fact: entries carry `available` with `unavailable_reasons`, so some workflows can be non-runnable, plus a `credits_estimate`. The rest of the sentence enumerates return fields (inputs, outputs, steps), which duplicates the existing output schema rather than adding new behavioral context.

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 definition and examples, then the routing guidance, then the parameter hint - a sensible order with no filler sentences. The middle clause enumerating every returned field is the least valuable part given an output schema exists, but it is compressed into one sentence.

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?

A read-only, zero-required-parameter list tool with an output schema needs little more than purpose and a filter hint, and both are present. The gap is minor: no indication of result size, pagination, or how to act on `unavailable_reasons` (e.g., whether another workflow variant is substitutable).

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 0% and the schema is a bare string-or-null with no enum, so the description carries the full burden. It compensates well by naming the accepted values 'Filter by `category` (image, video, audio)', which the schema does not supply. It does not say whether the filter is exact-match or whether omitting it returns all workflows, but the essential semantics are present.

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 states what a workflow is ('multi-step pipelines built on the capabilities') and gives concrete examples (text-to-clip, product-to-ad, effect presets), which distinguishes it clearly from generate and list_capabilities. It never explicitly says it returns a list, but the category filter and enumerated fields make the listing action unambiguous.

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?

'Prefer a workflow over chaining generate calls by hand when one fits' is an explicit when-to-use rule with a named alternative, which is the key routing decision here. It does not mention when to prefer get_workflow, run_workflow, or estimate_workflow instead, so guidance stops short of full coverage.

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.

Resources