VideoGenerationMCP

Overview Schema Source Related Servers Discussions Admin

generate_seedance_first_last

Generate a short video by providing a first frame image, an optional last frame, and a text prompt to describe the motion.

Instructions

Generate a Seedance video from a first (and optional last) frame image.

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": {
      "prompt": "<prompt>",
      "image_first": "<image_first>"
    },
    "name": "generate_seedance_first_last"
  }
}

Input Schema

Name	Required	Default
`wait`	No
`prompt`	Yes
`duration`	No
`task_type`	No	seedance-2
`image_last`	No
`resolution`	No	720p
`image_first`	Yes
`service_mode`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations, the description must explain side effects, async behavior, and requirements. It only says 'Generate a Seedance video' and gives no information about task creation, waiting, resolution, or other behavioral traits. This is a significant gap for a generation tool.

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?

A single, focused sentence that immediately states the verb and resource. It is front-loaded, avoids redundancy, and contains no filler. The structure is appropriately minimal for the limited information it conveys.

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

Completeness2/5

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

For a tool with 8 parameters and no annotations, the description is far from complete. It fails to mention the significance of the wait flag, service_mode, task lifecycle, or how the first/last frames are used. Even though an output schema exists, the operational context remains unclear.

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 description coverage is 0%, and the description only indirectly references image_first and image_last. It does not explain any of the other six parameters (prompt, duration, wait, resolution, task_type, service_mode), nor their defaults or interactions. The description adds minimal value over the raw 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?

The description clearly identifies the action ('Generate a Seedance video') and the specific input modality (first/optional last frame image). It distinguishes this tool from text-to-video generation by emphasizing the frame images, though it doesn't explicitly contrast with the sibling tool 'generate_seedance_video'.

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 description implies the tool is for using start and end frame images to generate video, but it provides no explicit guidance on when to choose this over alternatives like generate_seedance_video. No context, prerequisites, or exclusions are given.

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