jimeng_visual_generation

generate_image

Generate images from text prompts or modify reference images with AI. Choose from various aspect ratios and set random seeds for consistent results.

Instructions

Generate images using Volcengine visual generation API.

CRITICAL INSTRUCTIONS FOR AI AGENTS:

For image size, ONLY use the 'size' parameter (e.g., size="16:9"). DO NOT pass a 'ratio' or 'width'/'height' parameter.
If the user provides a custom Endpoint ID (starts with 'ep-'), you MUST pass it into the 'model' parameter.

Capabilities:

Text-to-Image: Provide 'prompt' and 'size'.
Image-to-Image: Provide 'prompt' AND 'image_urls' (list containing 1 image string).

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": {
      "params": "<params>"
    },
    "name": "generate_image"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Jul 13, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations exist, so the description carries full burden. It discloses critical parameter behaviors (e.g., 'model' should be omitted unless custom endpoint) and mode-specific requirements. However, it does not mention rate limits, authentication, or idempotency, leaving some gaps.

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?

The description is well-structured with sections for critical instructions and capabilities. It is efficient but slightly verbose in the instructions section; however, every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (two modes, multiple constraints), the description covers essential usage details. The presence of an output schema reduces the need to describe return values, making the description complete.

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

Parameters5/5

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

The description adds significant context beyond the input schema, such as the prohibition of 'ratio' and the rule for 'model'. It also explains the relationship between parameters for different modes, enhancing understanding of parameter usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates images using a specific API. It lists two capabilities (text-to-image and image-to-image), and sibling tools ('generate_video', 'get_video_task_result') are distinct, making the purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit instructions: use 'size' parameter only, avoid 'ratio'/'width'/'height', and pass custom endpoint IDs to 'model'. It also explains when to use each mode based on provided parameters, offering clear guidance.

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

Deploy Server