Magic Hour

Get video project

get_video_project

Read-only

Returns a video project's status and, once complete, its download URLs. Use to check progress with the id from a video create tool. Read-only.

Input Schema

Name	Required	Description	Default
`id`	Yes	Unique ID of the video project. This value is returned by all of the POST APIs that create a video.

Output Schema

Name	Required	Description
`id`	Yes	Unique ID of the video. Use it with the [Get video Project API](https://docs.magichour.ai/api-reference/video-projects/get-video-details) to fetch status and downloads.
`fps`	Yes	Frame rate of the video. If the status is not 'complete', the frame rate is an estimate and will be adjusted when the video completes.
`name`	Yes	The name of the video.
`type`	Yes	The type of the video project. Possible values are ANIMATION, AUTO_SUBTITLE, VIDEO_TO_VIDEO, FACE_SWAP, TEXT_TO_VIDEO, IMAGE_TO_VIDEO, LIP_SYNC, TALKING_PHOTO, AVATAR, VIDEO_UPSCALER, VIDEO_EDITOR, CHARACTER_REPLACE, VIDEO_COLORIZER, VIDEO_WATERMARK_REMOVER, VIDEO_COLOR_GRADER, VIDEO_TRANSLATOR, MUSIC_VIDEO, EXTEND, AUDIO_TO_VIDEO, VIDEO_EXPANDER, UGC_AD
`error`	Yes	In the case of an error, this object will contain the error encountered during video render
`width`	Yes	The width of the final output video. A value of -1 indicates the width can be ignored.
`height`	Yes	The height of the final output video. A value of -1 indicates the height can be ignored.
`status`	Yes	The status of the video. - `draft` - the project was created but has not been submitted for rendering - `queued` - the job is waiting for an available server - `rendering` - the job is being processed; the `video.started` webhook event fires when rendering begins - `complete` - the job finished successfully; fires `video.completed` - `error` - the job failed during processing; fires `video.errored` - `canceled` - the job was manually canceled (for example from the Magic Hour web app) Note: `rendering`, `complete`, and `error` have matching webhook events; `canceled` does not - a canceled job emits no webhook event, so poll this endpoint to detect cancellation.
`enabled`	Yes	Whether this resource is active. If false, it is deleted.
`downloads`	Yes
`created_at`	Yes
`end_seconds`	Yes	End time of your clip (seconds). Must be greater than start_seconds.
`start_seconds`	Yes	Start time of your clip (seconds). Must be ≥ 0.
`credits_charged`	Yes	The amount of credits deducted from your account to generate the video. If the status is not 'complete', this value is an estimate and may be adjusted upon completion based on the actual FPS of the output video. If video generation fails, credits will be refunded, and this field will be updated to include the refund.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the trailing "Read-only." sentence is pure restatement of structured data and earns no credit. What the description does add — that the response carries status first and download URLs only once the job completes — is genuinely useful behavioral context not expressed by annotations, but it's thin for a status/polling tool.

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?

Three short sentences, front-loaded with what is returned, then how to use it, then a safety tag. Nothing is padded and no sentence is wasted, aside from the redundant read-only line.

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?

This is a simple one-parameter read with full schema coverage and an output schema, so return values need not be explained. The description covers the essentials, though for a status-checking tool it could note whether the call blocks or returns immediately, which is what would separate it from wait_for_video_project.

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% and the single `id` property is already well documented, including its provenance from the create APIs. The description repeats that provenance ("the id from a video create tool") but adds no format, validation, or failure-mode detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Returns a video project's status ... download URLs") and clarifies the staged nature of the response. It implicitly positions itself against fetch_video_download (URLs vs. the actual download) and wait_for_video_project, but never names those siblings, so a caller still has to infer the split.

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?

"Use to check progress with the id from a video create tool" gives clear context and even names the source of the required id. It stops short of the 5 bar because it offers no exclusions — notably it never says when to use wait_for_video_project instead of repeatedly polling this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Magic Hour tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.