Skip to main content
Glama

sora_generate_video_with_character

Generate a new video featuring an animated character extracted from a reference video. Place the character in a new scene described by your prompt.

Instructions

Generate an AI video featuring a character from a reference video.

This allows you to create new videos featuring a specific character
extracted from another video. The character will be placed in the
new scene described by the prompt.

IMPORTANT: The reference video must NOT contain real people.
Only animated or digital characters are supported.

Use this when:
- You want to reuse a character in different scenes
- You're creating a series with the same character
- You want consistent character appearance across videos

Returns:
    Task ID and generated video information including URLs and state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of the video to generate featuring the character. Describe the scene and action.
character_urlYesURL of the video containing the character to use. IMPORTANT: The video must NOT contain real people, only animated/digital characters.
character_startNoStart position of the character in the reference video (0-1 range). For example, 0.2 means the character appears at 20% from the start.
character_endNoEnd position of the character in the reference video (0-1 range). For example, 0.8 means the character ends at 80% of the video.
modelNoSora model version. 'sora-2' or 'sora-2-pro' for higher quality.sora-2
sizeNoVideo resolution. 'small' for lower resolution, 'large' for higher resolution.large
durationNoVideo duration in seconds. Options: 10, 15, or 25 (25 only for sora-2-pro).
orientationNoVideo orientation. 'landscape', 'portrait'.landscape

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool requires a reference video with an animated character, generates a new video, and returns a task ID and video info. However, it does not mention generation time, potential failures, or costs, which would improve transparency.

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?

The description is well-structured: a one-line summary, a clarifying paragraph, an important note, a 'Use this when' bullet list, and a return statement. Every sentence adds value; no fluff or redundancy.

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

Completeness4/5

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

Given the tool's complexity (8 parameters, output schema exists), the description covers purpose, usage, and high-level returns. It does not explain the output schema in detail (but output schema exists), nor error handling. It is reasonably complete but could be improved by mentioning asynchronous behavior or typical generation times.

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

Parameters4/5

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

Schema coverage is 100% with good descriptions, so the description adds moderate value by explaining the overall effect (character placed in new scene). The description does not repeat parameter details but contextualizes them, justifying a score above baseline.

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 it generates an AI video featuring a character from a reference video, using a specific verb ('Generate') and resource ('video with character'). It distinguishes from siblings like 'sora_generate_video' by explicitly focusing on character reuse.

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 usage guidance: 'Use this when: You want to reuse a character in different scenes, creating a series, want consistent character appearance.' It also highlights a constraint ('reference video must NOT contain real people'), helping the agent decide when to use this tool.

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/SoraMCP'

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