Skip to main content
Glama

list_workflows

List pre-loaded workflow templates shipped with the ComfyUI MCP server to use as baselines for image generation and processing tasks.

Instructions

List built-in workflow templates shipped with this MCP server. These are the named workflows that can be used as a baseline; for arbitrary workflows use generate_with_workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler/definition of the 'list_workflows' tool. It registers an MCP tool named 'list_workflows' on the server, takes no arguments (empty schema), and returns a list of built-in workflow names from BUILTIN_WORKFLOWS.
    server.tool(
      "list_workflows",
      "List built-in workflow templates shipped with this MCP server. These are the named workflows that can be used as a baseline; for arbitrary workflows use generate_with_workflow.",
      {},
      async () => {
        const body = BUILTIN_WORKFLOWS.map(
          (name, i) => `  ${i + 1}. ${name}`,
        ).join("\n");
        return {
          content: [
            {
              type: "text" as const,
              text: `Built-in workflows (${BUILTIN_WORKFLOWS.length}):\n${body}`,
            },
          ],
        };
      },
  • The input schema for 'list_workflows' — an empty object literal `{}`, meaning the tool accepts no arguments.
    {},
  • Definition of BUILTIN_WORKFLOWS: the constant array of workflow names ['txt2img', 'img2img', 'upscale', 'controlnet', 'ip_adapter'] that the 'list_workflows' tool reads from.
    export const BUILTIN_WORKFLOWS = [
      "txt2img",
      "img2img",
      "upscale",
      "controlnet",
      "ip_adapter",
    ] as const;
  • src/server.ts:45-45 (registration)
    Registration call: `registerModelTools(s, client)` is invoked in buildContext() to register the 'list_workflows' (and 'list_models') tools on the MCP server.
    registerModelTools(s, client);
  • The export function `registerModelTools` that wires up the tool registration (called from server.ts).
    export function registerModelTools(
      server: McpServer,
      client: ComfyUIClient,
    ): void {
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the tool lists built-in templates, which is straightforward, but offers no details about side effects, permissions, or behavior in edge cases.

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?

The description is highly concise—two sentences with no wasted words. It is front-loaded with the main purpose and immediately provides an alternative for a related use case.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with no parameters, no output schema, and no annotations, the description provides the core purpose and a usage alternative. However, it lacks clarity on how this tool differs from the sibling 'list_workflow_templates', leaving some contextual gaps.

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 input schema has no parameters, so schema coverage is 100%. The description adds no parameter information, which is acceptable given there are no parameters to document. Baseline score of 4 is appropriate.

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 clearly states it lists built-in workflow templates, using a specific verb ('List') and resource ('workflow templates'). However, it fails to differentiate from the sibling tool 'list_workflow_templates', which may cause confusion.

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?

The description explicitly tells when not to use this tool ('for arbitrary workflows use generate_with_workflow'), but does not address when to use the similar sibling 'list_workflow_templates'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/miller-joe/comfyui-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server