Skip to main content
Glama

sora_generate_video_async

Generate AI videos asynchronously via webhook callbacks. Submit requests and receive automatic notifications when complete, avoiding blocking waits for long-running video generation.

Instructions

Generate an AI video asynchronously with callback notification.

This is useful for long-running video generation tasks. Instead of waiting
for the video to complete, you'll receive a callback at your specified URL
when the generation is finished.

Use this when:
- You don't want to wait for the generation to complete
- You have a webhook endpoint to receive results
- You're integrating with an async workflow

The callback will receive a POST request with the same response format
as the synchronous generation tools.

Returns:
    Task ID that you can use to correlate with the callback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of the video to generate.
callback_urlYesURL to receive the callback when video generation is complete. The result will be POSTed to this URL as JSON.
modelNoSora model version.sora-2
sizeNoVideo resolution.large
durationNoVideo duration in seconds.
orientationNoVideo orientation.landscape
image_urlsNoOptional list of reference image URLs for image-to-video generation.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full disclosure burden and successfully explains the async lifecycle: callback mechanism (POST request), response format (same as synchronous tools), and correlation method (Task ID). Missing error handling or timeout specifics, but covers core behavioral traits well.

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 sections: opening statement, rationale, bullet-point usage conditions, callback details, and Returns block. Front-loaded with the core purpose. Slightly verbose in 'Use this when' section but remains scannable and purposeful.

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 async complexity and 100% schema coverage, the description adequately covers the critical async-specific context (callback URL requirement, task correlation, response format). Since an output schema exists (per context signals), the brief mention of Task ID return value is sufficient.

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 has 100% description coverage (all 7 parameters documented), establishing baseline 3. The description references 'specified URL' and 'long-running' tasks, adding workflow context, but does not elaborate on parameter semantics (e.g., enum choices for model/size) 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 explicitly states it 'Generate[s] an AI video asynchronously with callback notification,' using a specific verb and resource. It clearly distinguishes from synchronous siblings by emphasizing 'long-running' tasks and the async callback mechanism instead of waiting for completion.

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?

Provides explicit 'Use this when:' bullets listing webhook availability and async workflow integration. Implies contrast with synchronous alternatives by stating 'Instead of waiting for the video to complete,' though it doesn't explicitly name the sync sibling tool (sora_generate_video) as the alternative.

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