AetherWave Studio

Reframe video to a new aspect ratio (Luma Ray 2 Flash)

aetherwave_reframe_video

Reframes a video to a new aspect ratio by intelligently outpainting/cropping the edges. Pass a public videoUrl and target reframeAspectRatio. 17 credits per second. Optional reframePrompt lets you steer the new edge content (e.g. 'extend the sky with sunset clouds'). Returns the reframed video URL (R2-hosted).

Returns within ~45 s. If the result has state "running" the job is still rendering: poll aetherwave_get_job with the returned taskId and kind every ~10 s. Pass wait:true ONLY if your MCP client permits tool calls longer than 60 s (most do not). Pass async:true to get the taskId back immediately without waiting.

Input Schema

TableJSON Schema

Name	Required	Description
`wait`	No	Block until the job finishes (up to the tool's full budget, 6-15 minutes). ONLY if your MCP client permits tool calls longer than 60 s; most abandon the call at 60 s and lose the taskId. Default false: return within ~45 s and hand back a taskId if still running.
`async`	No	Submit and return the taskId immediately without polling at all. Then poll aetherwave_get_job(taskId, kind).
`videoUrl`	Yes	Public URL of the source video (MP4).
`reframePrompt`	No	Optional prompt to steer the new edge content.
`reframeAspectRatio`	Yes	Target aspect ratio.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedInput schema / properties / async

Added value: +{
+  "description": "Submit and return the taskId immediately without polling at all. Then poll aetherwave_get_job(taskId, kind).",
+  "type": "boolean"
+}

addedInput schema / properties / wait

Added value: +{
+  "description": "Block until the job finishes (up to the tool's full budget, 6-15 minutes). ONLY if your MCP client permits tool calls longer than 60 s; most abandon the call at 60 s and lose the taskId. Default false: return within ~45 s and hand back a taskId if still running.",
+  "type": "boolean"
+}

First observedJun 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: cost (17 credits per second), expected latency (~45 s), the meaning of the 'running' state, which tool to poll and at what interval, and the client-timeout hazard of wait:true. Annotations only cover the safety profile (openWorld, non-idempotent, non-destructive), so this operational detail is genuinely additive.

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?

Front-loads what the tool does and its cost before the polling mechanics; every sentence carries either a constraint or a recovery instruction. The wait/async material is slightly redundant with the schema descriptions, but it is not wasted length.

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?

With no output schema, the description still covers the return value (R2-hosted reframed video URL), the fallback taskId, the 'running' state, and the exact recovery path. Nothing an agent needs to invoke and follow through on the job is missing.

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%, so baseline is 3; the description nevertheless adds value by naming videoUrl, reframeAspectRatio and reframePrompt and giving a concrete steering example ('extend the sky with sunset clouds'), plus restating the wait/async contract with the failure mode it avoids.

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?

States a specific verb+resource ('Reframes a video to a new aspect ratio') and explains the mechanism ('intelligently outpainting/cropping the edges'), which distinguishes it from the sibling aetherwave_reframe_image and from aetherwave_generate_video. An agent can route to it without opening the schema.

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 explicit operational guidance: poll aetherwave_get_job every ~10 s when state is 'running', use wait:true only if the client supports >60 s calls, use async:true otherwise. It does not contrast itself with the sibling reframe/generate tools, so sibling-level when-to-use is left implicit.

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

All AetherWave Studio 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?