Zhenzhen Image MCP

generate_image

Generate or edit images from text prompts and reference images, then save the results to disk using selectable GPT Image models.

Instructions

同步生成并落盘。默认逆向五参数；官转须显式 group=official。收费，POST 不自动重试。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>",
      "model": "<model>"
    },
    "name": "generate_image"
  }
}

Input Schema

Name	Required	Description	Default
`size`	No	可选 auto 或 WIDTHxHEIGHT；两边为16倍数、最大3840、比例不超过3:1、总像素655360..8294400。省略时不发送。
`group`	No	分组声明：默认 reverse（逆向）；仅用户明确使用官转时传 official。此字段不发送上游、不改变密钥后台分组。	reverse
`model`	Yes	GPT Image 2.5 Sunburst 非常适合对编辑精度要求极高的应用场景；GPT Image 2.5 Flare 是目前用于生成高质量图片的最快模型。模型可以接受文本和图片作为输入，然后输出相应的图片。以上为用户提供的供应商选型说明，尚未做速度或质量对比实测。请结合用户意图选择并告知所用模型。
`images`	No
`prompt`	Yes
`quality`	No
`output_dir`	No	可选绝对输出目录；默认配置目录。异步任务查询默认沿用提交目录。
`idempotency_key`	No	可选稳定幂等键；相同参数复用，参数改变拒绝，禁止换键重试未知收费结果。
`official_options`	No	仅 group="official" 可用的官转扩展参数。未声明官转时传入此对象会在收费前拒绝。

Output Schema

Name	Required	Description	Default
`cost`	No
`note`	No
`files`	No
`group`	No
`usage`	No
`reused`	No
`status`	Yes
`task_id`	No
`warning`	No
`progress`	No
`response`	No
`next_tool`	No
`output_dir`	No
`fail_reason`	No
`save_status`	No
`wait_timed_out`	No
`download_errors`	No
`idempotency_key`	No
`auto_poll_interval`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.4.0Oct 23, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[A-Za-z0-9_-]{1,128}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "可选稳定幂等键；相同参数复用，参数改变拒绝，禁止换键重试未知收费结果。",
+  "title": "Idempotency Key"
+}

addedOutput schema / properties / auto_poll_interval

Added value: +{
+  "title": "Auto Poll Interval",
+  "type": "integer"
+}

addedOutput schema / properties / idempotency_key

Added value: +{
+  "title": "Idempotency Key",
+  "type": "string"
+}

addedOutput schema / properties / reused

Added value: +{
+  "title": "Reused",
+  "type": "boolean"
+}

First observedv0.3.0Oct 20, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, but the description adds genuinely new behavior: the operation is synchronous, it writes files to disk, it is billed ('收费'), and failed POSTs are not retried automatically. These are important operational details an agent cannot derive from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the synchronous-save behavior, so no sentence is wasted. However, the telegraphic jargon ('五参数', '官转', 'POST') makes it less accessible than a slightly longer, clearer phrasing would be.

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 9-parameter, cost-incurring generation tool, the description covers the highest-risk facts (billing, no auto-retry, persistence) and an output schema exists, so return values need no explanation. It still omits routing guidance versus the many submit_* siblings and any hint about model selection or image-input expectations.

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 coverage is 67%, so most parameters are documented. The description reinforces the critical group=official requirement, but '默认逆向五参数' is never explained and adds no actionable meaning beyond the schema's own group description. The remaining parameters are left entirely to the schema.

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 opening sentence '同步生成并落盘' states a specific verb (generate synchronously) and outcome (persist to disk), which clearly distinguishes it from the async submit_* siblings. The phrase '默认逆向五参数' is cryptic, but the core purpose is unmistakable.

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?

It gives one conditional rule for the group parameter ('官转须显式 group=official') and a retry warning, but never states when to choose this tool over submit_image_generation, submit_image_batch, or edit_image. The routing decision is left to inference.

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

Deploy Server