Skip to main content
Glama
veniceai

Venice MCP Server

Official
by veniceai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Venice Image Edit

venice_image_edit

Edit an image from a URL using a text prompt, with optional model, aspect ratio, and output format settings. Returns base64 PNG and supports wallet or API key auth.

Instructions

Edit an image with a prompt. Returns base64 PNG. Supports x402 wallet auth (no Venice account needed) and API key.

Input Schema

NameRequiredDescriptionDefault
modelNoEdit model id; defaults to firered-image-edit.
promptYes
image_urlYesURL of the image to edit (will be passed through to the edit endpoint).
safe_modeNo
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 image. May add time and cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 image. May add time and cost.",
+  "type": "boolean"
+}
    • addedInput schema / properties / output_format
      Added value: +{
+  "enum": [
+    "jpeg",
+    "jpg",
+    "png",
+    "webp"
+  ],
+  "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.1/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive mutation. The description adds genuinely useful context beyond that: the base64 PNG return format and the dual-auth model (no Venice account required via x402). It stops short of cost, latency, or reversibility details.

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?

Three short sentences, each front-loaded with the most important fact (action, return value, auth). No filler or repetition.

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 an 8-parameter mutation with no output schema, the description usefully covers the return format and auth, but leaves a meaningful gap around the undocumented parameters and the relationship between prompt/enhance_prompt and the input image.

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?

At 63% schema coverage, several parameters (prompt, safe_mode, output_format) lack descriptions in the schema, and the tool description adds no parameter meaning at all. It doesn't clarify defaults, model-specific validation, or how the prompt interacts with the input image despite enhance_prompt hinting at that relationship.

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 an image with a prompt") and adds the return format (base64 PNG). It does not, however, distinguish itself from close siblings like venice_image_multi_edit, venice_image_remove_bg, or venice_image_upscale, so an agent must infer the boundary.

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?

The description names the supported auth modes (x402 wallet vs API key) but gives no guidance on when to choose this over image_generate, image_multi_edit, or other image siblings, and no exclusions or prerequisites. Usage is only implied by the verb.

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