Skip to main content
Glama

sora_generate_video_v2_async

Generate AI videos asynchronously using Sora V2 with webhook callbacks. Submit prompts to receive an immediate task ID, then get results POSTed to your callback URL when generation completes.

Instructions

Generate an AI video asynchronously using Sora Version 2 with callback.

Similar to sora_generate_video_v2 but returns immediately with a task ID.
The result will be POSTed to your callback URL when generation completes.

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

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
durationNoVideo duration in seconds. Options: 4, 8, or 12.
sizeNoVideo resolution in pixels.1280x720
image_urlsNoOptional list of reference image URLs. Only the first image is used.

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. It successfully explains the async lifecycle (returns immediately, POSTs result to callback, returns Task ID for correlation). Minor gap: does not mention error handling, retry behavior, or callback timeout policies.

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?

Excellent structure with one-line summary, sibling differentiation, technical mechanism, usage bullets, and return value. Every sentence provides distinct value (purpose, comparison, behavior, guidelines, output). No redundancy or filler.

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 6 parameters, async complexity, and existence of output schema (per context signals), description provides sufficient detail: explains the async contract, distinguishes from sync alternative, and notes the Task ID return value without needing to replicate full output schema documentation.

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 enums and defaults. Description mentions 'callback URL' reinforcing the required parameter, but does not add semantic meaning beyond what the schema already provides for the 6 parameters. Baseline 3 appropriate for high-coverage schemas.

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-resource combination ('Generate an AI video asynchronously using Sora Version 2') and immediately distinguishes from sibling tool sora_generate_video_v2 via the comparison sentence. Clear scope includes the callback mechanism.

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?

Explicit 'Use this when:' section lists three specific scenarios (non-blocking requirements, webhook availability, async workflows). Also explicitly references the synchronous alternative (sora_generate_video_v2) for comparison.

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