Zhenzhen Image MCP

edit_image

Apply text-prompt edits to one or more images and save the generated results to disk synchronously.

Instructions

同步图像编辑并落盘；多图以 image[] 上传。高编辑精度场景建议 Sunburst。收费。

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>",
      "images": "<images>"
    },
    "name": "edit_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`	Yes	本机绝对图片路径、公开 HTTP(S) 图片 URL 或 base64 data URL；PNG/JPEG/WebP。
`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

A3.6/5.0

Behavior4/5

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

Annotations already flag openWorld and non-idempotent, and the description adds genuinely new behavior: it is synchronous, it persists files to disk, and it is billed ('收费'). It stops short of saying what happens on failure or how billing scales, but the value-add over annotations is real.

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

Conciseness4/5

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

Four short clauses, no filler, and the sync/disk/billing facts are front-loaded. The telegraphic style omits subjects and reads as terse notes rather than prose, but nothing is wasted.

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?

An output schema covers return values, but for a billed, non-idempotent, 9-parameter mutation the description should say more about cost implications and failure/retry behavior. The one-word '收费' signals a charge exists without qualifying it.

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 78%, so the baseline is 3. The description only touches multi-image input (and names it 'image[]' while the actual parameter is 'images') and model choice; the model guidance largely duplicates the model parameter's own description.

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?

States a specific verb+resource ('同步图像编辑') plus two distinguishing traits: it is synchronous and it writes results to disk ('落盘'). This separates it from async siblings like submit_image_edit without naming them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a model-selection cue ('高编辑精度场景建议 Sunburst') and implies sync-vs-async usage via '同步', but never states when to prefer submit_image_edit, submit_image_batch, or generate_image instead. Usage is implied rather than routed.

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

Deploy Server