Skip to main content
Glama

Reframe image to a new aspect ratio (Ideogram V3 Reframe)

aetherwave_reframe_image

Reframe images to any aspect ratio by intelligently outpainting edges. Provide a public image URL and target ratio like '16:9' or '1:1'. Choose speed: turbo, balanced, or quality. Returns the reframed image URL.

Instructions

Reframes an image to a new aspect ratio by intelligently outpainting the edges. Pass a public imageUrl and the target aspectRatio ('16:9', '9:16', '1:1', '4:3', '3:4', etc.). Three speed tiers: 'turbo' (5 cr, fast), 'balanced' (10 cr, default), 'quality' (14 cr, slowest, best edges). Returns the reframed image URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageUrlYesPublic URL of the source image.
aspectRatioYesTarget aspect ratio (e.g. '16:9', '9:16', '1:1', '4:3', '3:4', '21:9').
speedNoRendering speed. 'turbo'=5cr, 'balanced'=10cr (default), 'quality'=14cr.
Behavior4/5

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

Annotations indicate non-readonly and non-destructive behavior. The description adds valuable transparency: it specifies the outpainting approach, speed tiers with credit costs, and that it returns a URL. No contradictions with annotations.

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 sentences, each purposeful: first defines the core action, second lists required parameters, third details optional parameters with costs. No redundant information.

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?

The description covers inputs, behavior (outpainting), optional parameters, and output (URL). It lacks details on potential limitations (e.g., image size constraints) but is sufficiently complete for typical use given the tool's moderate complexity.

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%, but the description enhances understanding by providing examples for aspectRatio ('16:9', '9:16', etc.) and clarifying the meaning of each speed tier with its credit cost. This goes beyond the schema's basic descriptions.

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?

The description uses a specific verb ('reframes an image to a new aspect ratio') and resource ('image'), and clearly differentiates from the sibling 'aetherwave_reframe_video' tool. It states the intelligently outpainting behavior, making the purpose unmistakable.

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

Usage Guidelines3/5

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

The description tells how to use the tool (pass imageUrl and aspectRatio) and explains speed tier options with costs. However, it does not explicitly state when to use this tool over alternatives like 'edit_image' or 'upscale_image', leaving room for ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AetherWave-Studio/aetherwave-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server