Magic Hour MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

audio_projects_retrieve_details

Check audio project status and retrieve download URLs after render completes, including error details if rendering fails.

Instructions

Check the progress of a audio project. The downloads field is populated after a successful render.

Statuses

queued — waiting to start
rendering — in progress
complete — ready; see downloads
error — a failure occurred (see error)
canceled — user canceled
draft — not used

MCP guidance:

Use this after a create tool to poll job status. When status is complete, surface the downloads URLs to the user; if status is error, surface the error message.
Each downloads[n].url is already the full signed download URL. Use it exactly as returned. Do not shorten it, strip query parameters, or append expires_at onto the URL string.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Unique ID of the audio. Use it with the [Get audio Project API](https://docs.magichour.ai/api-reference/audio-projects/get-audio-details) to fetch status and downloads.
`name`	Yes	The name of the audio.
`type`	Yes	The type of the audio project. Possible values are AUDIO_TRANSLATOR, VOICE_GENERATOR, VOICE_CHANGER, VOICE_CLONER, VIDEO_TO_AUDIO, MUSIC_GENERATOR, SOUND_EFFECT_GENERATOR
`error`	Yes	In the case of an error, this object will contain the error encountered during video render
`status`	Yes	The status of the audio. - `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 `audio.started` webhook event fires when rendering begins - `complete` - the job finished successfully; fires `audio.completed` - `error` - the job failed during processing; fires `audio.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
`credits_charged`	Yes	The amount of credits deducted from your account to generate the audio. We charge credits right when the request is made. If an error occurred while generating the audio, credits will be refunded and this field will be updated to include the refund.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden, and it does so thoroughly. It discloses the full status lifecycle, explains that `downloads` is populated only after a successful render, describes the `error` field, and warns that download URLs are signed and must be used exactly as returned. This goes well beyond the bare operation name.

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 longer than average but well-organized with a status list and a separate MCP guidance block. Each section serves a purpose, though there is mild redundancy between 'downloads is populated after render' and the guidance to surface downloads on complete.

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?

For a simple one-parameter retrieval tool, the description covers all necessary operational context: status meanings, what to surface to the user, and exactly how to handle signed download URLs. Given the output schema exists upstream, the description does not need to enumerate return fields and is complete for invocation.

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?

There is only one parameter and the schema description coverage is 100%. The schema already explains `id` as a unique ID returned by POST APIs. The description does not add param-specific semantics beyond referring to the audio project, but it doesn't need to because the schema is complete.

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 opens with a specific verb and resource: 'Check the progress of a audio project.' It also clarifies that the `downloads` field appears after a successful render collectively with a status list. However, it does not explicitly differentiate itself from the sibling `wait_for_audio_project`, which likely polls the same resource, so it is clear but not fully differentiated.

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?

The MCP guidance explicitly states when to use it: 'Use this after a create tool to poll job status.' It also tells the agent what to do on completion or error. It lacks a 'when not to use' or references to alternatives like `wait_for_audio_project`, so it has clear context but no exclusions.

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

Deploy Server