Skip to main content
Glama
qmediat

ideogram-mcp

by qmediat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Ad resizer

ideogram_ad_resizer

Resize and reframe ads to exact platform ad dimensions, keeping creative inside published safe zones and optionally editing during the resize.

Instructions

Reframe an ad to a platform's exact ad size (resolution WIDTHxHEIGHT from the list; platform picks the published safe zone), optionally editing while reframing. Takes the creative as a local file, a public https URL or an Ideogram asset. 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)
promptNoWhat to create or change, in natural language
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
platformNoThe ad platform whose published safe zone the ad stays inside (google, meta, meta_reels, meta_stories, snapchat, tiktok)
num_imagesNoHow many outputs to make (each is billed)
resolutionNoExact output size WIDTHxHEIGHT from the model's list; not with aspect_ratio
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.5.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does a decent job: it states that results are written to the output directory rather than returned inline, and that long-running jobs surface as a generation_id rather than a finished image. It doesn't disclose billing/permission implications or what happens to the source creative, but the operational behavior is well covered.

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?

Three dense sentences, front-loaded with the core action before input formats and downstream routing. Every sentence carries information, though the parenthetical lists make it slightly heavy.

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 10-parameter tool with no output schema, the description covers input formats, output destination, async fallback, and the related pricing/generation tools. The main omission is guidance on sibling selection among the other ad/edit tools.

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 ten parameters in detail. The description reinforces a few points (resolution must come from the list, platform selects the safe zone, the creative can be a file, https URL, or Ideogram asset) but adds little beyond what the schema states. Baseline 3 is appropriate.

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 and resource ('Reframe an ad to a platform's exact ad size') and scopes it tightly to ad sizing with the platform safe zone, which separates it from the general ideogram_reframe sibling. An agent can identify the job 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 clear routing context: use ideogram_quote to price first, and that long jobs hand back a generation_id for ideogram_generation. It does not explicitly say when to prefer this over ideogram_reframe or ideogram_ad_localizer, so the sibling distinction is left implicit.

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

Deploy Server

Other Tools