Skip to main content
Glama

midjourney_extend_video

Extend an existing Midjourney video by generating additional frames based on your prompt. Continue the story or motion to create a longer clip.

Instructions

Extend an existing Midjourney video to make it longer.

This allows you to continue a previously generated video by adding more
frames based on your prompt description.

Use this when:
- You want to make a video longer
- You want to continue the story or motion from an existing video
- You need to add more content to a short clip

Returns:
    Task ID and extended video information including new video URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_idYesID of the video to extend. This is the 'video_id' field from a previous video generation result.
promptYesDescription for the video extension. This guides how the video should continue.
video_indexNoIndex of the video to extend from the video_urls array. 0-indexed, default is 0 (first video).
modeNoGeneration mode.fast
end_image_urlNoOptional URL of an image to use as the final frame of the extended video.
callback_urlNoWebhook callback URL for asynchronous notifications. When provided, the API will call this URL when the video extension is complete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It mentions the async callback_url behavior and return values but does not disclose whether the operation is destructive, required permissions, or rate limits. The description is adequate but not fully transparent.

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 concise with a clear structure: a one-line purpose, a brief explanation, a bulleted use case list, and a return description. It is front-loaded and easy to scan.

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?

Given the tool has 6 parameters and an output schema (implied), the description adequately explains the return values but lacks details on error handling, limitations, or prerequisites. It is sufficient for a moderately complex tool.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description adds general context about extending videos but does not provide new meaning beyond the schema definitions. It could elaborate on how parameters like end_image_url affect the output.

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 states it extends an existing Midjourney video to make it longer, using a specific verb and resource. However, it does not directly differentiate from sibling tools like midjourney_generate_video, though the context implies it is for extending rather than creating.

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

Usage Guidelines4/5

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

The 'Use this when:' list provides three explicit scenarios for when to use the tool, offering clear context. It does not mention when not to use it or alternatives, but the guidance is still helpful.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/MidjourneyMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server