Skip to main content
Glama

sora_generate_video_with_character

Generate AI videos by extracting animated or digital characters from reference videos and placing them in new scenes. Create consistent video series with unified character appearance across multiple clips.

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 provided, so description carries full burden. Discloses critical content policy constraint ('reference video must NOT contain real people'), reveals extraction/placement mechanism, and notes Task ID return implying async job pattern. Minor gap: doesn't explicitly clarify sync vs async behavior despite async siblings existing.

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?

Well-structured with clear hierarchy: purpose → mechanism → critical constraint → usage scenarios → returns. Front-loaded with core function. Slight redundancy in 'Returns' section since output schema exists, but the Task ID mention is valuable for indicating async behavior.

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?

Appropriately comprehensive for 8-parameter tool with content safety requirements. Covers purpose, constraints, usage patterns, and return values. Given existence of output schema and high schema coverage, description successfully addresses the complex character-extraction workflow without overwhelming verbosity.

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 has 100% coverage (baseline 3). Description adds value by contextualizing the extraction workflow ('character extracted from another video', 'placed in the new scene') and emphasizing the real-person restriction for character_url parameter. Elevates above baseline schema documentation.

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?

Opens with specific verb ('Generate') and resource ('AI video featuring a character from a reference video'). Explicitly distinguishes from siblings by emphasizing character extraction from existing video, contrasting with generic generation (sora_generate_video) or image-based generation (sora_generate_video_from_image).

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?

Contains explicit 'Use this when:' section with three specific scenarios (reuse character in different scenes, creating series, consistent appearance). This clearly differentiates appropriate use cases from generic video generation alternatives.

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

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