Magic Hour MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

photo_colorizer_create_image

Colorize black-and-white photos by providing an image file path or URL. Each conversion costs 10 credits and runs asynchronously.

Instructions

Colorize image. Each image costs 10 credits.

MCP guidance:

This starts an async image generation job and returns id plus credits_charged immediately. If the user wants the finished result, call the wait_for_image_project helper with the returned id, or poll the matching GET /v1/image-projects/{id} endpoint until status is complete, error, or canceled. Completed projects include downloads with direct URLs. The custom wait helper also returns exact_download_urls separately from expiration metadata.
For *_file_path values, prefer an existing Magic Hour file path or a file_path returned by the upload-URL endpoint after the file bytes are uploaded. Direct public media URLs may work when they are stable, fetchable, and return raw file bytes, but hotlinked URLs can fail; when in doubt, use the presigned upload flow first and pass the returned file_path.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Give your image a custom name for easy identification.	Photo Colorizer - dateTime
`assets`	Yes	Provide the assets for photo colorization

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Unique ID of the image. Use it with the [Get image Project API](https://docs.magichour.ai/api-reference/image-projects/get-image-details) to fetch status and downloads.
`credits_charged`	Yes	The amount of credits deducted from your account to generate the image. We charge credits right when the request is made. If an error occurred while generating the image(s), 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.2/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explicitly explains that this is an async job, returns id and credits_charged immediately, requires polling or the wait_for_image_project helper, and describes terminal statuses and download URLs. It also discloses the cost and file-path reliability caveats.

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?

The description is front-loaded with the core purpose and cost, then organized into concise, relevant MCP guidance bullets. Every sentence adds operational value, and there is no redundant restatement of schema fields.

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 async generation workflow, nested assets object, and use of external upload endpoints, the description is complete. It covers job lifecycle, polling/waiting behavior, download access, file upload semantics, and cost while leaving return-value details to the existing output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes both parameters at 100% coverage, and the description adds meaningful extra guidance beyond the schema. It explains how to supply *_file_path values correctly, preferring Magic Hour paths or upload-URL file_path values, and warns that hotlinked URLs can fail with a recommended presigned upload fallback.

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 action and resource: 'Colorize image.' This clearly identifies what the tool does, and the name photo_colorizer_create_image reinforces the intent. However, it does not explicitly differentiate itself from sibling image-generation tools, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description gives operational guidance about async behavior and file paths, but it does not explain when to choose this tool over alternatives like ai_image_editor_create_image or ai_image_generator_create_image. It notes the 10-credit cost but offers no usage conditions or exclusions.

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

Deploy Server