Skip to main content
Glama

comfyui_create_workflow

Read-onlyIdempotent

Create a ComfyUI workflow from a template (txt2img, img2img, etc.) with optional parameter overrides for prompt, size, steps, and more.

Instructions

Create a ComfyUI workflow from a template with optional parameter overrides.

    Available templates: ``txt2img``, ``img2img``, ``upscale``, ``inpaint``,
    ``txt2vid_animatediff``, ``txt2vid_wan``, ``controlnet_canny``,
    ``controlnet_depth``, ``controlnet_openpose``, ``ip_adapter``,
    ``lora_stack``, ``face_restore``, ``flux_txt2img``, ``sdxl_txt2img``.

    Args:
        template (required): Template name from the list above.
        params (optional): JSON string of parameter overrides. Defaults to
            an empty string, meaning "use template defaults". Pass either
            ``""`` or ``"{}"`` for no overrides. Common keys:
            ``prompt``, ``negative_prompt``, ``width``, ``height``,
            ``steps``, ``cfg``, ``model``, ``denoise``, ``controlnet_model``,
            ``control_strength``, ``lora_name``, ``lora_strength``.

    Example:
        ``comfyui_create_workflow(template="txt2img",
        params='{"prompt": "a sunset", "width": 768, "steps": 30}')``
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo
templateYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context about parameter overrides and default behavior ('Pass either "" or "{}" for no overrides'), but it does not explicitly state that the workflow is not executed, which would further clarify side effects.

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 well-organized with a clear purpose statement, a bulleted list of templates, an Args section, and a usage example. Every element adds value, and the structure makes it easy to scan and understand.

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?

Given the complexity of the tool (multiple templates and JSON parameters), the description is highly complete. It covers all necessary inputs, defaults, constraints, and provides an example. The presence of an output schema means return values do not need to be explained in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description fully compensates. It lists all valid template names, explains that params is a JSON string, documents common keys, provides default behavior, and gives a concrete example. This is exemplary parameter documentation.

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 begins with a specific verb+resource: 'Create a ComfyUI workflow from a template with optional parameter overrides.' It clearly distinguishes this from sibling tools like comfyui_run_workflow and comfyui_generate_image by focusing on creation rather than execution or generation.

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 clearly communicates when to use this tool: to create a workflow from one of the listed templates. It does not explicitly mention alternatives or exclusions, but the template list and example imply that this is the right choice for workflow creation, not execution.

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/hybridindie/comfyui_mcp'

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