Skip to main content
Glama

sora_generate_video_v2

Generate short AI videos with precise pixel-resolution control using Sora Version 2. Choose from 4, 8, or 12 second durations and specific sizes like 1280x720.

Instructions

Generate an AI video using Sora Version 2 (partner channel).

Version 2 offers shorter video durations (4/8/12 seconds) with
precise pixel-based resolution control. This is ideal for quick
video generation with specific resolution requirements.

Use this when:
- You need precise pixel resolution control (e.g., 1280x720)
- You want shorter videos (4, 8, or 12 seconds)
- You want to use the partner channel for generation

For longer videos (10-25 seconds) or character-based generation,
use the version 1 tools (sora_generate_video, etc.) instead.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of the video to generate. Be descriptive about the scene, action, style, and mood.
modelNoSora model version. 'sora-2' is standard, 'sora-2-pro' offers higher quality.sora-2
durationNoVideo duration in seconds. Options: 4, 8, or 12.
sizeNoVideo resolution in pixels. Options: '720x1280' (vertical), '1280x720' (horizontal), '1024x1792' (tall vertical), '1792x1024' (wide horizontal).1280x720
image_urlsNoOptional list of reference image URLs. Only the first image is used for version 2. Image dimensions should match the size parameter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so the description must carry full burden. It mentions returns Task ID and video info, but does not disclose behavioral traits like rate limits, auth needs, cost implications, or error handling. Slightly below average for a version-specific 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?

Well-structured and concise: front-loaded with purpose, then usage conditions, then alternatives. No wasted sentences; every sentence earns its place.

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 complexity (5 params, all described in schema), presence of output schema, and clear distinction from 8 sibling tools, the description is complete. It provides sufficient context for correct selection and invocation.

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%, so baseline 3. The description adds value by explaining that version 2 offers shorter durations and precise resolution, and that image_urls only uses the first image for v2 and should match size. This goes beyond schema.

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 AI videos using Sora Version 2, emphasizing shorter durations and precise pixel resolution control. It distinguishes from sibling tools by contrasting with version 1 tools for longer videos/character generation.

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?

Explicitly states when to use (precise resolution, shorter videos, partner channel) and when not to use (longer videos/character generation, pointing to version 1 tools). Names alternative tools (sora_generate_video, etc.).

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