Skip to main content
Glama

sora_get_task

Retrieve video generation status and results from Sora tasks. Check if generation is pending, succeeded, or failed, and get video URLs with complete metadata.

Instructions

Query the status and result of a video generation task.

Use this to check if a generation is complete and retrieve the resulting
video URLs and metadata.

Use this when:
- You want to check if a generation has completed
- You need to retrieve video URLs from a previous generation
- You want to get the full details of a generated video

Task states:
- 'pending': Generation is still in progress
- 'succeeded': Generation finished successfully
- 'failed': Generation failed (check error message)

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task ID returned from a video generation request. This is the 'task_id' field from any sora_generate_* tool response.

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. Excellently discloses the task state machine ('pending', 'succeeded', 'failed') and mentions error messages for failed states. Could improve by describing behavior for invalid task_ids or polling frequency recommendations.

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?

Perfectly structured with hierarchical sections: one-line purpose, high-level usage, bullet-pointed usage triggers, state definitions, and return value summary. No redundant text; 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 tool's single-parameter simplicity and existence of output schema, the description is complete. It covers the async lifecycle states essential for polling workflows and indicates what information the output contains without duplicating the full output schema.

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 for the single 'task_id' parameter, explaining it comes from sora_generate_* responses. Description adds no additional parameter semantics, which is acceptable given the complete 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?

Description opens with specific verb 'Query' and clear resource 'video generation task'. Implicitly distinguishes from generation siblings (sora_generate_*) by focusing on status checking rather than creation, and from batch retrieval (sora_get_tasks_batch) via singular 'task' focus.

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:' section with three clear scenarios (checking completion, retrieving URLs, getting details). Implicitly excludes generation use cases, but does not explicitly name the batch retrieval alternative (sora_get_tasks_batch) for multiple tasks.

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