Skip to main content
Glama

list_workflow_templates

Retrieve a catalog of all saved workflow templates in the registry, enabling users to browse, select, and reuse predefined workflows.

Instructions

List all saved workflow templates in the registry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function for the 'list_workflow_templates' tool. It reads the templates directory, filters .json files, parses StoredTemplate metadata (name, description, updatedAt), and returns a formatted list.
    server.tool(
      "list_workflow_templates",
      "List all saved workflow templates in the registry.",
      listSchema,
      async () => {
        let entries: string[];
        try {
          entries = await fs.readdir(store.dir);
        } catch {
          return {
            content: [
              {
                type: "text" as const,
                text: `No templates directory at ${store.dir} yet.`,
              },
            ],
          };
        }
        const names = entries
          .filter((f) => f.endsWith(".json"))
          .map((f) => f.replace(/\.json$/, ""));
        if (names.length === 0) {
          return {
            content: [
              { type: "text" as const, text: "No templates saved yet." },
            ],
          };
        }
        const rows: string[] = [];
        for (const name of names.sort()) {
          try {
            const raw = await fs.readFile(
              templatePath(store.dir, name),
              "utf-8",
            );
            const t = JSON.parse(raw) as StoredTemplate;
            const desc = t.description ? ` — ${t.description}` : "";
            rows.push(`  ${t.name}${desc} (updated ${t.updatedAt})`);
          } catch {
            rows.push(`  ${name} (unreadable)`);
          }
        }
        return {
          content: [
            {
              type: "text" as const,
              text: `Saved templates (${names.length}) in ${store.dir}:\n${rows.join("\n")}`,
            },
          ],
        };
      },
  • The schema for list_workflow_templates — an empty object (no input parameters required).
    const listSchema = {};
  • src/server.ts:48-48 (registration)
    The registration call: registerTemplateTools(s, client, templateStore) is invoked during server construction, which registers all template tools including 'list_workflow_templates' on the MCP server.
    registerTemplateTools(s, client, templateStore);
  • The registerTemplateTools function that registers 'list_workflow_templates' (and other template tools) onto the McpServer instance via server.tool().
    export function registerTemplateTools(
      server: McpServer,
      client: ComfyUIClient,
      store: TemplateStore,
    ): void {
      server.tool(
Behavior3/5

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

The description implies a read-only listing but does not explicitly state behavior such as pagination, ordering, or if the list is exhaustive. Without annotations, more detail would improve transparency.

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?

A single, clear sentence with no unnecessary words. It is front-loaded and efficiently conveys the tool's purpose.

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?

Given zero parameters and no output schema, the description is mostly adequate. However, it lacks specification of the return format, which could be helpful for an agent.

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?

No parameters exist, and the schema description coverage is 100%. The description adds nothing about parameters, which is acceptable since there are none to document.

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 clearly states the action ('List') and resource ('all saved workflow templates in the registry'), distinguishing it from siblings like 'get_workflow_template' (single) and 'run_workflow_template' (execution).

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?

No guidance on when to use this tool versus alternatives; for example, it doesn't note that 'get_workflow_template' is for retrieving a single template's details.

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