Skip to main content
Glama

批量生图 / 改图

create_images

Generate or edit images from text prompts or reference image paths, running up to eight jobs concurrently and returning paste-ready Markdown image links.

Instructions

生成或修改图片。任务带 images 走图生图,不带走文生图,多任务自动并发。 返回可直接粘贴的 Markdown 图片引用。参数或排版不确定先调 info。

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": "create_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo所有任务的默认张数。
jobsNo任务数组,最多 8 个。只有一个任务时改用顶层 prompt 简写。
sizeNo所有任务的默认精确像素。
modelNo所有任务的默认模型。
ratioNo所有任务的默认比例。
imagesNo单任务简写:参考图路径。
outputNo单任务简写:写到哪,规则同任务里的 output。例 "兔子" / "E:/图/兔子/三视图.png"。
promptNo单任务简写:画什么。仅在 jobs 为空时生效。
qualityNo所有任务的默认质量档。
animatedNo所有任务的默认动画开关:true 出多帧 GIF,规则见任务级同名参数。
resolutionNo所有任务的默认清晰度档。
concurrencyNo并发路数,默认 3。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry the full burden. It discloses meaningful behavior: automatic concurrent execution across tasks and a returned value that is a ready-to-paste Markdown image reference. It does not describe disk-write side effects, cost, or failure modes; the deeper timing and error notes live in the schema rather than in the description.

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?

Four short sentences are front-loaded with the core action and the img2img versus text-to-image split, with no filler. Every sentence, including the pointer to `info`, adds something the agent can act on.

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?

For a 12-parameter tool with a nested `jobs` array, a 100% documented schema, and no output schema, the description covers routing, output format, and escalation to `info`. It is slightly thin on how top-level shorthand relates to `jobs`, but that gap is filled by the schema.

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 every parameter is already documented. The `images`→img2img rule in the description largely restates the schema's own wording. Baseline 3 is appropriate because the schema already does the heavy lifting.

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 states a specific verb and resource combination (

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?

It gives a clear routing rule: if `images` is provided, use img2img; if not, use text-to-image. It also tells the agent to call the `info` sibling when parameters or layout are uncertain. It does not state when the tool should not be used or how to choose between the shorthand and `jobs` array, although the schema covers that choice.

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

Deploy Server

Other Tools