Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice Image Multi-Edit

venice_image_multi_edit

Edit up to eight images together with one prompt for multi-image composition or outpainting, returning a base64 PNG via API key or x402 wallet authentication.

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.

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": {
      "image_urls": "<image_urls>",
      "prompt": "<prompt>"
    },
    "name": "venice_image_multi_edit"
  }
}

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
Behavior4/5

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

Annotations already cover the operation profile (openWorldHint, non-idempotent, non-destructive), and the description adds genuinely useful context beyond them: the output is a base64 payload and two auth paths exist (x402 wallet or API key, no Venice account required). Minor gap: the 'Returns base64 PNG' claim is not reconciled with the output_format enum that also permits jpeg/webp.

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?

Three short sentences, purpose front-loaded, no filler. The 'Returns base64 PNG' sentence earns its place but should have been qualified to avoid implying PNG-only output.

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?

With 8 parameters, no output schema, and half the schema undocumented, the definition covers purpose, return shape, and auth but leaves parameter behavior and cost/pricing implications (explicitly flagged in the quality and enhance_prompt schemas) unaddressed. Adequate, not complete.

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?

Schema coverage is only 50% across 8 parameters, so the description needs to compensate and does not. It never explains model, resolution, output_format, enhance_prompt, or limits like the 8-image max or whether image_urls accept remote URLs only — the only parameter-adjacent statement is the PNG return claim, which conflicts with the enum.

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 and resource ('edit multiple images together with a single prompt') and clarifies the capability as multi-image composition / outpainting. The word 'multiple' implicitly distinguishes it from sibling venice_image_edit, but no sibling is named 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?

'Multiple images' plus 'multi-image composition / outpainting' implies when to pick this over venice_image_edit or venice_image_generate, but the description never says so directly and offers no exclusions or prerequisites.

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