Skip to main content
Glama

sora_generate_video

Generate AI videos from a text prompt. Describe the scene, action, style, and mood to produce a video matching your description.

Instructions

Generate an AI video from a text prompt using Sora.

This is the primary way to create videos - describe what you want and Sora
will generate a video matching your description.

Use this when:
- You want to generate a video from a text description
- You don't have reference images
- You want creative AI-generated video content

For image-to-video generation, use sora_generate_video_from_image instead.
For character-based video generation, use sora_generate_video_with_character.

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. Examples: 'A cat running on the river', 'A futuristic cityscape with flying cars at sunset', 'A person walking through a snowy forest'
modelNoSora model version. 'sora-2' is the standard model. 'sora-2-pro' offers higher quality and supports 25-second videos.sora-2
sizeNoVideo resolution. 'small' for lower resolution, 'large' for higher resolution.large
durationNoVideo duration in seconds. Options: 10, 15, or 25 (25 only available with sora-2-pro model).
orientationNoVideo orientation. 'landscape' for horizontal (16:9), 'portrait' for vertical (9:16).landscape

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 description carries full burden. It states it returns Task ID and video info, but does not disclose behavioral traits like whether generation is synchronous, rate limits, or what happens on failure. It is decent but could be more transparent.

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 concise with a clear first sentence stating purpose, followed by bullet-point usage guidelines and a return statement. No redundant information.

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 complexity (5 parameters) and presence of output schema, the description covers purpose, usage, and return. It could mention asynchronous behavior but is largely complete.

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?

Input schema has 100% description coverage with detailed parameter descriptions, so baseline is 3. The tool description does not add extra parameter semantics beyond what the schema already provides.

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 AI video from a text prompt using Sora. It uses specific verbs and resource (generate video from prompt) and distinguishes itself from siblings by naming alternatives for image-to-video and character-based 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?

The description provides explicit when-to-use conditions (text description, no reference images, creative content) and names specific alternative tools (sora_generate_video_from_image, sora_generate_video_with_character), fully guiding tool selection.

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