Skip to main content
Glama

OpenAI Videos Create

openai-videos-create
Read-only

Create a video from a text prompt with optional image reference via OpenAI's API. Returns the video job object and downloads video, thumbnail, or spritesheet.

Instructions

Create a video generation job using the OpenAI Videos API. Returns structuredContent with the OpenAI Video job object, and (optionally) downloaded assets as MCP content blocks (tool_result=resource_link|resource).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesText prompt that describes the video to generate (max 32K chars).
input_referenceNoOptional image reference: HTTP(S) URL, base64 / data URL, or file path.
input_reference_fitNoHow to fit input_reference to the requested video size: match (require exact), cover (crop), contain (pad), stretch (distort). Default: contain.contain
input_reference_backgroundNoPadding background when input_reference_fit=contain: blur (default), black, white, or hex color (#RRGGBB/#RRGGBBAA).blur
modelNoVideo model to use (default: sora-2-pro).sora-2-pro
secondsNoClip duration in seconds (default: 4 seconds).
sizeNoOutput resolution formatted as width x height. Sizes 1024x1792 and 1792x1024 require sora-2-pro.
wait_for_completionNoIf true, poll the job until completed/failed (then optionally download assets). Default: true.
timeout_msNoMax time to wait for completion when wait_for_completion is true (default: 900000).
poll_interval_msNoPolling interval when wait_for_completion is true (default: 2000).
download_variantsNoWhich downloadable assets to fetch when completed (default: ['video']).
tool_resultNoControls content[] shape: 'resource_link' (default) emits ResourceLink items, 'resource' emits EmbeddedResource blocks with base64 blob.resource_link
Behavior1/5

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

The description claims the tool creates a video job, which is a write operation, but the annotations declare readOnlyHint=true, indicating a read-only operation. This is a direct contradiction, making the description misleading. Additionally, the description does not disclose behavioral traits like job lifecycle or side effects beyond annotations.

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?

The description is two sentences long and covers the core action and output. It is efficient and front-loaded with the primary purpose, though it could be improved by structuring the output behavior more explicitly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (12 parameters, no output schema), the description lacks essential context about job lifecycle, polling behavior, and exact return format. It mentions optional downloads but does not explain how the agent should handle job status or errors, leaving significant gaps.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no additional parameter-level information beyond what the schema provides, meeting the baseline for this dimension.

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's action ('create a video generation job'), specifies the API (OpenAI Videos API), and describes the return value (structuredContent with job object and optional assets). This distinguishes it from sibling tools like openai-videos-retrieve or openai-videos-delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating new video generation jobs, but lacks explicit guidance on when to use this tool versus alternatives like openai-videos-remix or google-videos-generate. No when-not-to-use conditions or prerequisites are provided.

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/strato-space/media-gen-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server