trident-mcp

Overview Schema Source Related Servers Discussions Admin

image_to_image

Destructive

Edit or derive images from one or more reference images and return a Tripo task ID for follow-up; use prompts or templates to guide changes before 3D conversion.

Instructions

Edit or derive an image from one or more reference images. Creates a Tripo task (spends credits) and returns its task_id immediately; then call wait_for_task.

Input Schema

TableJSON Schema

Name	Required	Description
`size`	No	Output size: 2K, 4K or WxH such as 2048x2048 (default)
`input`	No	The source image: local path, URL, file token or image task ID
`model`	No	Image model: seedream_v4 (text_to_image default), seedream_v5 (image_to_image default), banana, banana2, banana_pro, chat_image_2, chat_image_2.5_flare, chat_image_2.5_sunburst. See list_models
`inputs`	No	Several reference images, referenced in the prompt as image[1], image[2], ... (seedream up to 4, banana up to 10, chat_image up to 16)
`prompt`	No	The edit to make. Required unless template is set
`quality`	No	chat_image models only (default low); xhigh and max need a 2.5 model
`template`	No	Preset edit, e.g. 3d_enhance to prepare a photo for image_to_model
`background`	No	chat_image 2.5 models only; transparent needs output_format png
`aspect_ratio`	No	banana models only (default 1:1); 1:8, 1:4, 4:1 and 8:1 need banana2
`output_format`	No	Image file format (default png)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`model`	No
`task_id`	Yes
`produces`	Yes
`warnings`	No
`operation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedv0.4.0Oct 19, 2026

addedInput schema / properties / aspect_ratio

Added value: +{
+  "description": "banana models only (default 1:1); 1:8, 1:4, 4:1 and 8:1 need banana2",
+  "enum": [
+    "1:1",
+    "2:3",
+    "3:2",
+    "3:4",
+    "4:3",
+    "4:5",
+    "5:4",
+    "9:16",
+    "16:9",
+    "21:9",
+    "1:8",
+    "1:4",
+    "4:1",
+    "8:1"
+  ],
+  "type": "string"
+}

addedInput schema / properties / background

Added value: +{
+  "description": "chat_image 2.5 models only; transparent needs output_format png",
+  "enum": [
+    "auto",
+    "opaque",
+    "transparent"
+  ],
+  "type": "string"
+}

removedInput schema / properties / height

Removed value: -{
-  "description": "Optional output height",
-  "type": "integer"
-}

removedInput schema / properties / imagePath

Removed value: -{
-  "description": "Local image path to upload as input",
-  "type": "string"
-}

removedInput schema / properties / imageUrl

Removed value: -{
-  "description": "Public image URL to use as input",
-  "type": "string"
-}

changedInput schema / properties / input / description

Previous value: -"Image URL or file token. Mutually exclusive with imagePath and imageUrl"New value: +"The source image: local path, URL, file token or image task ID"

addedInput schema / properties / inputs

Added value: +{
+  "description": "Several reference images, referenced in the prompt as image[1], image[2], ... (seedream up to 4, banana up to 10, chat_image up to 16)",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedInput schema / properties / model / description

Previous value: -"Image model, for example seedream_v5, gemini-3-pro, or chat_image_2"New value: +"Image model: seedream_v4 (text_to_image default), seedream_v5 (image_to_image default), banana, banana2, banana_pro, chat_image_2, chat_image_2.5_flare, chat_image_2.5_sunburst. See list_models"

removedInput schema / properties / negativePrompt

Removed value: -{
-  "description": "What to avoid in the generated image",
-  "type": "string"
-}

addedInput schema / properties / output_format

Added value: +{
+  "description": "Image file format (default png)",
+  "enum": [
+    "png",
+    "jpeg"
+  ],
+  "type": "string"
+}

changedInput schema / properties / prompt / description

Previous value: -"Edit prompt"New value: +"The edit to make. Required unless template is set"

addedInput schema / properties / quality

Added value: +{
+  "description": "chat_image models only (default low); xhigh and max need a 2.5 model",
+  "enum": [
+    "low",
+    "medium",
+    "high",
+    "xhigh",
+    "max"
+  ],
+  "type": "string"
+}

removedInput schema / properties / seed

Removed value: -{
-  "description": "Optional deterministic seed",
-  "type": [
-    "null",
-    "integer"
-  ]
-}

changedInput schema / properties / size / description

Previous value: -"Optional output size string"New value: +"Output size: 2K, 4K or WxH such as 2048x2048 (default)"

changedInput schema / properties / template / description

Previous value: -"Optional image-generation template"New value: +"Preset edit, e.g. 3d_enhance to prepare a photo for image_to_model"

addedInput schema / properties / template / enum

Added value: +[
+  "t_pose",
+  "character_completion",
+  "3d_enhance",
+  "variants",
+  "figure"
+]

removedInput schema / properties / width

Removed value: -{
-  "description": "Optional output width",
-  "type": "integer"
-}

addedOutput schema / properties / model
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / operation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / produces
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / taskId

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / task_id
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "taskId",
-  "status"
-]New value: +[
+  "task_id",
+  "operation",
+  "produces"
+]

Addedv0.3.0Jul 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the bar is lowered. The description nonetheless adds genuinely new behavioral facts: the call spends credits and is asynchronous (returns task_id immediately, requires wait_for_task).

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?

Two sentences with zero waste; the mutation/credit cost and async hand-off are front-loaded. Every clause earns its place.

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?

An output schema exists so return values need not be explained, and schema coverage is complete. The description covers the cost model and the required task->wait_for_task chaining, which is what an agent most needs to call correctly; only sibling-vs-sibling selection guidance is absent.

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% with per-parameter docs, enums, and defaults, so the schema carries the parameter burden and a baseline 3 applies. The description adds no parameter meaning beyond the schema — no guidance on model selection tradeoffs, input reference syntax, or prompt/template interplay.

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 ('Edit or derive an image') with the key scope qualifier 'from one or more reference images', which implicitly separates it from text_to_image. It does not explicitly distinguish image_to_image from the other image-input siblings (image_to_model, image_to_splat, image_to_multiview), whose differing output type is only inferable from the name.

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?

The async workflow is well covered ('returns its task_id immediately; then call wait_for_task'), which names the follow-up tool explicitly. However there is no guidance on when to choose this over text_to_image or the other image_* siblings, nor on which model/template to pick, so primary tool-selection guidance 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.