Skip to main content
Glama

Colorways

ideogram_colorways

Recolor a product photo using up to four masks with matching hex colors while preserving everything outside the masks. Accepts local files, HTTPS URLs, or Ideogram assets.

Instructions

Recolor a product photo: up to 4 masks, each paired by position with a six-digit hex colour; everything outside the masks is preserved. Takes the photo and the masks as local files, public https URLs or Ideogram assets. Results are saved to the output directory; long jobs come back as a generation_id for ideogram_generation; ideogram_quote prices a call first.

Input Schema

NameRequiredDescriptionDefault
imageNoThe source photo or ad to work on: a local image file or a public https URL (image_asset_identifier for an Ideogram asset)
masksNoLocal mask files (or public https URLs) marking the regions to change, paired by position (at most 4, the product photo's pixel size)
colorsNoOne target colour per mask as a six-digit hex code (#B3202C), paired by position with masks (at most 4)
wait_sNoSeconds to wait for the result (0-50, default 45). The job is accepted first; if it is still running when the wait ends, the result is its generation_id for ideogram_generation (never resubmitted, never billed twice).
privateNoKeep the result out of Ideogram's public feed; true unless you set false (enterprise accounts are always private)
qualityNolow, medium or high: higher may improve detail and takes longer
aspect_ratioNoOutput aspect ratio with a colon — 1:1, 3:4, 4:3, 16:9 or 9:16 where the operation lists them (colorways and material swap default to the photo's ratio, ghost mannequin and sketch to render to 1:1, pose variants to the nearest supported); magic prompt: the ratio to pin, or omitted for the model's pick
inline_imagesNotrue: each saved image is also returned as image content (base64; one over 3.75 MB, or past 10 MB in total, by path only), for a client without file access
image_asset_identifierNoAn Ideogram asset (an upload or an earlier result) instead of a local image
mask_asset_identifiersNoIdeogram assets as the masks, paired by position (at most 4)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.5.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses input formats, that results are saved to the output directory, that long jobs return a generation_id for ideogram_generation, and that ideogram_quote prices a call first. However, it omits permissions, reversibility, rate limits, and whether the original photo is modified.

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 compact, front-loaded with the core action, and every sentence adds useful information about inputs, outputs, and related tools. No filler or redundancy.

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?

For a complex tool with no output schema, the description covers what it does, accepted input formats, where results go, and async handling. It does not describe the output artifact format (e.g., image files vs. base64), but the key operational details are present.

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?

Schema description coverage is 100%, so the schema already documents all parameters; baseline is 3. The description adds minor value by reiterating the mask-to-colour positional pairing and accepted input types, but does not introduce meaning beyond the schema.

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 and resource ('Recolor a product photo') and details the mechanism (up to 4 masks paired with hex colours, everything outside preserved). It does not name or contrast with any sibling tool, so it falls short of the highest tier, but an agent can still identify the task unambiguously.

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 offers no guidance on when to use this tool versus alternatives like ideogram_material_swap or ideogram_edit. It provides procedural notes about long jobs and quoting, but nothing about selection criteria or exclusions.

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