Magic Hour

AI Image Upscaler

ai_image_upscaler_create_image

MCP guidance:

Starts an async image job; returns id and credits_charged. For finished results, call wait_for_image_project with that id or poll GET /v1/image-projects/{id} until complete, error, or canceled. Results include downloads; wait helpers add exact_download_urls. Preserve signed URLs and query parameters; never append expiration metadata.
For *_file_path, use an existing Magic Hour path or the upload-URL endpoint's file_path after uploading raw bytes to its presigned URL. Direct public media URLs may work if stable and fetchable as raw bytes; hotlinked URLs can fail. Prefer the upload-URL endpoint when unsure.

Upscale your image using AI. Each 2x upscale costs 50 credits for balanced/creative modes, and 25 credits for preserve. 4x upscale costs 200 and 100 credits respectively.

Input Schema

Name	Required	Description	Default
`name`	No	Give your image a custom name for easy identification.	Image Upscaler - dateTime
`style`	No	Style settings for the upscale. Use `mode` (`"preserve"`, `"balanced"`, or `"creative"`). Defaults to `"balanced"`.
`assets`	Yes	Provide the assets for upscaling
`scale_factor`	Yes	How much to scale the image. Must be either 2 or 4. Note: 4x upscale is only available on Creator, Pro, or Business tier.

Output 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.

Changed4 schema fields changedOct 12, 2026
- addedInput schema / properties / style / example
```
Added value: +{
+  "mode": "preserve"
+}
```
- changedInput schema / properties / style / properties / mode / example
```
Previous value: -"balanced"New value: +"preserve"
```
- addedInput schema / properties / style / properties / prompt / example
```
Added value: +"Enhance fine details and keep the image natural"
```
- changedOutput schema / properties / credits_charged / example
```
Previous value: -50New value: +25
```

Changed1 schema field changedSep 24, 2026

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
-  "type": "string"
-}

Changed1 schema field changedSep 11, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare openWorldHint=true and non-read-only, but the description adds substantial behavior: async execution model, the exact return fields (`id`, `credits_charged`), terminal job states, credit costs differentiated by mode and scale factor, a tier restriction on 4x, and the signed-URL handling rule ('preserve signed URLs and query parameters; never append expiration metadata'). This is genuine context the structured fields do not carry.

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?

Information is dense and largely front-loaded, with the lifecycle contract first and the purpose/cost sentence after. The 'MCP guidance' preamble is cross-tool boilerplate that would apply to many Magic Hour endpoints, and the file-path advice partially restates the schema, keeping this from a 5.

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?

An output schema exists so return values need not be re-explained, and the description nonetheless covers the async lifecycle, result retrieval path, cost model, credential/tier constraint, and URL-handling caveat. Combined with a fully-described nested schema for a 4-parameter tool, an agent has everything needed to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, establishing a baseline of 3. The description goes beyond the schema by mapping credit multipliers to modes (25 vs 50 credits) and to scale factor (200 vs 100 credits), which the schema does not state, and by reinforcing the `*_file_path` contract for uploaded assets.

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?

States a specific verb+resource: 'Upscale your image using AI', with concrete cost/scale detail (2x = 50/25 credits, 4x = 200/100). It does not explicitly differentiate itself from similarly-named siblings such as ai_image_editor_create_image or photo_colorizer_create_image, so an agent must infer the boundary from the name.

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?

Gives clear operational routing: the call starts an async job, and finished results require wait_for_image_project with the returned id or polling GET /v1/image-projects/{id}. It also advises preferring the upload-URL endpoint when unsure about file inputs. What it lacks is guidance about when to pick this tool over alternative image-modification siblings.

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.

Resources

Need Help?