Skip to main content
Glama

generate_image

Generate images from text prompts using ComfyUI's default txt2img workflow. Control output with prompt, negative prompt, dimensions, steps, CFG scale, seed, and checkpoint.

Instructions

Generate an image from a text prompt using ComfyUI's default txt2img workflow. Returns one or more image URLs served directly by the ComfyUI instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesText prompt describing the image to generate
negative_promptNoWhat to avoid in the image
widthNoImage width in pixels
heightNoImage height in pixels
stepsNoNumber of diffusion steps
cfgNoCFG / prompt adherence (1-30)
seedNoSeed for reproducibility
checkpointNoCheckpoint filename (defaults to COMFYUI_DEFAULT_CKPT)

Implementation Reference

  • The async handler function that executes the 'generate_image' tool logic. Calls client.generate() with prompt, negative_prompt, width, height, steps, cfg, seed, and checkpoint, then returns image URLs.
      async (args) => {
        const result = await client.generate({
          prompt: args.prompt,
          negativePrompt: args.negative_prompt,
          width: args.width,
          height: args.height,
          steps: args.steps,
          cfg: args.cfg,
          seed: args.seed,
          checkpoint: args.checkpoint,
        });
    
        return textResult(
          `Generated ${result.images.length} image(s) (prompt_id: ${result.promptId}):`,
          result.images,
        );
      },
    );
  • Zod schema defining input parameters for the 'generate_image' tool: prompt (string), negative_prompt (optional string), width (64-2048, default 1024), height (64-2048, default 1024), steps (1-150, default 25), cfg (1-30, default 7), seed (optional int), checkpoint (optional string).
    const generateImageSchema = {
      prompt: z
        .string()
        .min(1)
        .describe("Text prompt describing the image to generate"),
      negative_prompt: z.string().optional().describe("What to avoid in the image"),
      width: z
        .number()
        .int()
        .min(64)
        .max(2048)
        .default(1024)
        .describe("Image width in pixels"),
      height: z
        .number()
        .int()
        .min(64)
        .max(2048)
        .default(1024)
        .describe("Image height in pixels"),
      steps: z
        .number()
        .int()
        .min(1)
        .max(150)
        .default(25)
        .describe("Number of diffusion steps"),
      cfg: z
        .number()
        .min(1)
        .max(30)
        .default(7)
        .describe("CFG / prompt adherence (1-30)"),
      seed: z.number().int().optional().describe("Seed for reproducibility"),
      checkpoint: z
        .string()
        .optional()
        .describe("Checkpoint filename (defaults to COMFYUI_DEFAULT_CKPT)"),
    };
  • Registration of the 'generate_image' tool via server.tool() with name 'generate_image' and description. Part of the registerGenerateTools() function called from src/server.ts:42.
    export function registerGenerateTools(
      server: McpServer,
      client: ComfyUIClient,
    ): void {
      server.tool(
        "generate_image",
        "Generate an image from a text prompt using ComfyUI's default txt2img workflow. Returns one or more image URLs served directly by the ComfyUI instance.",
        generateImageSchema,
  • src/server.ts:42-52 (registration)
    Call site where registerGenerateTools() is invoked with the MCP server and ComfyUIClient instance to register the 'generate_image' tool.
        registerGenerateTools(s, client);
        registerRefineTool(s, client);
        registerUpscaleTool(s, client);
        registerModelTools(s, client);
        registerImageTools(s, client);
        registerConditioningTools(s, client);
        registerTemplateTools(s, client, templateStore);
        return s;
      };
      return { client, buildServer };
    }
  • The generate() method on ComfyUIClient that the handler calls. It builds a txt2img workflow via the txt2img() helper and runs it via runWorkflow().
    async generate(params: GenerateParams): Promise<GenerateResult> {
      const workflow = txt2img({
        prompt: params.prompt,
        negativePrompt: params.negativePrompt ?? "",
        width: params.width ?? 1024,
        height: params.height ?? 1024,
        steps: params.steps ?? 25,
        cfg: params.cfg ?? 7,
        seed: params.seed ?? Math.floor(Math.random() * 2 ** 32),
        checkpoint: params.checkpoint ?? DEFAULT_CHECKPOINT,
      });
      return this.runWorkflow(workflow);
    }
  • The txt2img() workflow builder that creates the ComfyUI node graph (KSampler, CheckpointLoaderSimple, EmptyLatentImage, CLIPTextEncode, VAEDecode, SaveImage) used by the 'generate_image' tool.
    export function txt2img(params: Txt2ImgParams): Workflow {
      return {
        "3": {
          class_type: "KSampler",
          inputs: {
            seed: params.seed,
            steps: params.steps,
            cfg: params.cfg,
            sampler_name: "euler",
            scheduler: "normal",
            denoise: 1,
            model: ["4", 0],
            positive: ["6", 0],
            negative: ["7", 0],
            latent_image: ["5", 0],
          },
        },
        "4": {
          class_type: "CheckpointLoaderSimple",
          inputs: { ckpt_name: params.checkpoint },
        },
        "5": {
          class_type: "EmptyLatentImage",
          inputs: { width: params.width, height: params.height, batch_size: 1 },
        },
        "6": {
          class_type: "CLIPTextEncode",
          inputs: { text: params.prompt, clip: ["4", 1] },
        },
        "7": {
          class_type: "CLIPTextEncode",
          inputs: { text: params.negativePrompt, clip: ["4", 1] },
        },
        "8": {
          class_type: "VAEDecode",
          inputs: { samples: ["3", 0], vae: ["4", 2] },
        },
        "9": {
          class_type: "SaveImage",
          inputs: { filename_prefix: "comfyui-mcp", images: ["8", 0] },
        },
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden. It only mentions returning image URLs, but omits behavioral traits like destruction, auth requirements, rate limits, cost, or generation time.

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 two sentences, front-loaded with purpose, and contains no redundant information. Every word is justified.

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?

Given no output schema and no annotations, the description is adequate for a simple tool but lacks details on return format (e.g., temporary URLs), generation duration, or error handling.

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 description coverage is 100%, so baseline is 3. The description adds no new information about parameters beyond what the schema already provides.

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 verb 'generate' and resource 'image', and specifies it uses 'ComfyUI's default txt2img workflow', distinguishing it from sibling tools like generate_with_controlnet or generate_with_workflow.

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?

The description does not explicitly state when to use this tool versus its siblings. There is no mention of scenarios for basic generation versus other variants, leaving the agent without guidance on tool selection.

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