Skip to main content
Glama
veniceai

Venice MCP Server

Official
by veniceai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Venice Image Multi-Edit

venice_image_multi_edit

Edit multiple images together with one prompt for multi-image composition or outpainting, returning base64 PNG.

Instructions

Edit multiple images together with a single prompt (multi-image composition / outpainting). Returns base64 PNG. Supports x402 wallet auth (no Venice account needed) and API key.

Input Schema

NameRequiredDescriptionDefault
modelNo
promptYes
qualityNoModel-specific quality tier; may change pricing.
image_urlsYes
resolutionNoModel-specific output resolution tier; the API validates supported values.
aspect_ratioNoOutput aspect ratio, e.g. "1:1", "16:9", "9:16", "4:5". Supported values vary by model; the API validates.
output_formatNo
enhance_promptNoRewrite the edit prompt with awareness of the input images. May add time and cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • addedInput schema / properties / aspect_ratio / description
      Added value: +"Output aspect ratio, e.g. \"1:1\", \"16:9\", \"9:16\", \"4:5\". Supported values vary by model; the API validates."
    • removedInput schema / properties / aspect_ratio / enum
      Removed value: -[
-  "1:1",
-  "16:9",
-  "9:16",
-  "4:3",
-  "3:4",
-  "21:9",
-  "9:21"
-]
    • addedInput schema / properties / enhance_prompt
      Added value: +{
+  "description": "Rewrite the edit prompt with awareness of the input images. May add time and cost.",
+  "type": "boolean"
+}
    • addedInput schema / properties / output_format
      Added value: +{
+  "enum": [
+    "jpeg",
+    "jpg",
+    "png",
+    "webp"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / quality
      Added value: +{
+  "description": "Model-specific quality tier; may change pricing.",
+  "enum": [
+    "low",
+    "medium",
+    "high"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / resolution
      Added value: +{
+  "description": "Model-specific output resolution tier; the API validates supported values.",
+  "type": "string"
+}
  2. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already disclose the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the bar is lower. The description adds genuinely useful context beyond them: the return format (base64 PNG) and two auth paths (x402 wallet without a Venice account, or API key). It omits any cost/latency caveat even though quality 'may change pricing' and enhance_prompt 'may add time and cost'.

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 tightly packed sentences with zero filler; the core capability is front-loaded and the auth/output facts follow. Every clause carries information.

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?

With no output schema, the description correctly states the return format (base64 PNG), and it covers the auth model that an agent must resolve before calling. It is close to complete, but leaves the undocumented model/resolution/output_format params and any cost implications to the schema and annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Eight parameters with only 50% schema description coverage: model, prompt, image_urls, and output_format have no schema description, and the tool description compensates for none of them. It only echoes prompt and image_urls implicitly through 'single prompt' and 'multiple images'. Below the baseline 3 because the description adds essentially no semantic detail over 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?

States a specific verb+resource (edit multiple images) plus the use cases (multi-image composition / outpainting). It implicitly separates itself from venice_image_edit via the 'multiple images' scope, but never names the sibling explicitly, so the differentiation is left to inference.

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 'multiple images together with a single prompt' framing implies when this is preferred over single-image tools, but there is no explicit guidance on when to pick this versus venice_image_edit, venice_image_generate, or venice_image_upscale. Usage is implied rather than stated.

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