Scenario MAI Image
Overview
MAI Image 2.5, Microsoft's image family on Scenario, splits into generation members (2.5, 2.5 Pro)
and instruction editors (2.5 Edit, 2.5 Pro Edit). The family trait is typography: in-image
headlines, labels, and taglines come back legible and placed where the prompt put them: the pick for
posters, packaging, covers, and key art that carry real copy. Discover members with search and
treat model_schema_get as the contract: the four agree on almost every field and disagree on the
one that carries the source image.
Connection and the core loop: see the scenario skill in this repo; model-agnostic image work
(sizing families, masks, upscales): the scenario-image skill. If a sibling skill named here is
missing from your available skills, load it with skill_get (Scenario MCP) or ask the user to
install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas
and flag the gap.
Quick reference
At authoring time (names from the live schema):
| Member |
Makes |
Source input |
Ratios |
| 2.5 |
txt2img |
none |
11, incl. 21:9 |
| 2.5 Pro |
txt2img |
none |
8 |
| 2.5 Edit |
img2img |
referenceImages, array of one |
8 |
| 2.5 Pro Edit |
img2img |
image, single file |
8 |
All four share prompt (4096 characters on 2.5 and Edit, 5000 on the Pro pair), aspectRatio (an
enum defaulting to auto), and numOutputs (1 to 4, each added image adds cost). No width, height,
seed, negative prompt, or mask field exists: aspectRatio is the only sizing control, and edits
target elements by naming them in prose. On the generators auto picks a ratio from the prompt; on
the editors it matches the source, so leave it there unless re-framing is the point.
Typography is the lever
Write prose sentences, not tag lists: the family reasons over subject, composition, materials,
lighting, and mood in that rough order. Wrap exact in-image copy in quotes so it renders verbatim,
and give each text block a role, a style, and a place ("the headline 'GAME DAY' in bold condensed
type across the top third"). Unquoted or vague copy comes back paraphrased or mangled, and many
small text blocks compete, so group them. At authoring time text rendering was tuned for English and
outputs landed near 1K, so plan a downstream upscale for print or hero use. Steering is
positive-only: explore with numOutputs 2 to 4 and refine the sentence rather than hunting for a
seed.
Editing: preserve first, one change
Both editors take one source image and a plain instruction, under different fields: Edit wants
referenceImages with exactly one asset id in an array, Pro Edit wants image as a single file.
Porting a parameter block between them breaks the run, so re-read the schema when switching.
Structure the prompt as what must stay unchanged, then one change, naming the exact element and its
exact new state, with replacement copy in quotes ("change the sign to 'OPEN 24/7', same font and
color"). Chain passes for several changes; edits hold identity well across iterations. The two
shared one public image-edit arena entry (top 3 at authoring time) while a Pro Edit asset cost about
four times an Edit asset, so dry_run both and start with Edit.
Worked example: a campaign poster, then a copy swap
search with target="models", query="mai image", public=true. Note the generation and edit
hits, e.g. model_microsoft-mai-image-2-5-pro and model_microsoft-mai-image-2-5-edit (live
hits at authoring time: re-discover each session).
model_schema_get on the generation pick: ratio list, prompt cap, defaults.
model_run with dry_run=true and
parameters={"prompt": "A photorealistic poster of a climber on a granite wall at dawn, warm rim light, the headline 'ASCEND' in tall condensed sans-serif across the top, a small tagline 'Hold your line' lower left, editorial sports aesthetic.", "aspectRatio": "2:3", "numOutputs": 4}.
numOutputs moves cost, so re-estimate after changing it.
- Repeat with
wait=false, then jobs_wait with the returned job id, re-called with
pending_job_ids on timeout, never a second model_run.
asset_display the four outputs and keep one asset id.
model_schema_get on the edit pick, then model_run with
parameters={"referenceImages": ["asset_x"], "prompt": "Keep the climber, lighting, and layout unchanged. Change only the headline to 'ASCEND HIGHER', same font, color, and placement."};
jobs_wait, then asset_display.
Common mistakes
- Carrying one editor's source field to the other:
referenceImages (array of exactly one) and
image (single file) are member-specific shapes.
- Leaving in-image copy unquoted: only quoted text renders verbatim.
- Stacking several edits in one instruction: one change per pass, then chain.
- Sending pixel sizes or a ratio the member lacks:
aspectRatio is an enum and the lists differ
(21:9, 5:4, and 4:5 lived on one member at authoring time).
- Re-running for a pixel-identical result: no seed exists; keep the winning asset and edit it
forward.
- Shipping the 1K output to print: upscale downstream (see the
scenario-image skill).
1---2name: scenario-mai-image3description: "Use when generating or editing images with Microsoft MAI Image models on Scenario via MCP: photoreal or stylized text-to-image with legible in-image typography, posters, packaging, magazine covers, ads, key art, or instruction-based editing such as text swaps, recoloring, object removal or replacement, background swaps, lighting changes, and full restyles. Keywords: MAI Image 2.5, 2.5 Pro, 2.5 Edit, 2.5 Pro Edit, Microsoft, txt2img, img2img, typography, text rendering, image edit."4license: MIT5metadata:6 source: https://skillmd.com/skills/scenario-labs/scenario-mai-image7---89# Scenario MAI Image1011## Overview1213MAI Image 2.5, Microsoft's image family on Scenario, splits into generation members (2.5, 2.5 Pro)14and instruction editors (2.5 Edit, 2.5 Pro Edit). The family trait is typography: in-image15headlines, labels, and taglines come back legible and placed where the prompt put them: the pick for16posters, packaging, covers, and key art that carry real copy. Discover members with `search` and17treat `model_schema_get` as the contract: the four agree on almost every field and disagree on the18one that carries the source image.1920Connection and the core loop: see the `scenario` skill in this repo; model-agnostic image work21(sizing families, masks, upscales): the `scenario-image` skill. If a sibling skill named here is22missing from your available skills, load it with `skill_get` (Scenario MCP) or ask the user to23install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas24and flag the gap.2526## Quick reference2728At authoring time (names from the live schema):2930| Member | Makes | Source input | Ratios |31| ------------ | ------- | ------------------------------- | -------------- |32| 2.5 | txt2img | none | 11, incl. 21:9 |33| 2.5 Pro | txt2img | none | 8 |34| 2.5 Edit | img2img | `referenceImages`, array of one | 8 |35| 2.5 Pro Edit | img2img | `image`, single file | 8 |3637All four share `prompt` (4096 characters on 2.5 and Edit, 5000 on the Pro pair), `aspectRatio` (an38enum defaulting to `auto`), and `numOutputs` (1 to 4, each added image adds cost). No width, height,39seed, negative prompt, or mask field exists: `aspectRatio` is the only sizing control, and edits40target elements by naming them in prose. On the generators `auto` picks a ratio from the prompt; on41the editors it matches the source, so leave it there unless re-framing is the point.4243## Typography is the lever4445Write prose sentences, not tag lists: the family reasons over subject, composition, materials,46lighting, and mood in that rough order. Wrap exact in-image copy in quotes so it renders verbatim,47and give each text block a role, a style, and a place ("the headline 'GAME DAY' in bold condensed48type across the top third"). Unquoted or vague copy comes back paraphrased or mangled, and many49small text blocks compete, so group them. At authoring time text rendering was tuned for English and50outputs landed near 1K, so plan a downstream upscale for print or hero use. Steering is51positive-only: explore with `numOutputs` 2 to 4 and refine the sentence rather than hunting for a52seed.5354## Editing: preserve first, one change5556Both editors take one source image and a plain instruction, under different fields: Edit wants57`referenceImages` with exactly one asset id in an array, Pro Edit wants `image` as a single file.58Porting a parameter block between them breaks the run, so re-read the schema when switching.59Structure the prompt as what must stay unchanged, then one change, naming the exact element and its60exact new state, with replacement copy in quotes ("change the sign to 'OPEN 24/7', same font and61color"). Chain passes for several changes; edits hold identity well across iterations. The two62shared one public image-edit arena entry (top 3 at authoring time) while a Pro Edit asset cost about63four times an Edit asset, so `dry_run` both and start with Edit.6465## Worked example: a campaign poster, then a copy swap66671. `search` with `target="models"`, `query="mai image"`, `public=true`. Note the generation and edit68 hits, e.g. `model_microsoft-mai-image-2-5-pro` and `model_microsoft-mai-image-2-5-edit` (live69 hits at authoring time: re-discover each session).702. `model_schema_get` on the generation pick: ratio list, prompt cap, defaults.713. `model_run` with `dry_run=true` and72 `parameters={"prompt": "A photorealistic poster of a climber on a granite wall at dawn, warm rim light, the headline 'ASCEND' in tall condensed sans-serif across the top, a small tagline 'Hold your line' lower left, editorial sports aesthetic.", "aspectRatio": "2:3", "numOutputs": 4}`.73 `numOutputs` moves cost, so re-estimate after changing it.744. Repeat with `wait=false`, then `jobs_wait` with the returned job id, re-called with75 `pending_job_ids` on timeout, never a second `model_run`.765. `asset_display` the four outputs and keep one asset id.776. `model_schema_get` on the edit pick, then `model_run` with78 `parameters={"referenceImages": ["asset_x"], "prompt": "Keep the climber, lighting, and layout unchanged. Change only the headline to 'ASCEND HIGHER', same font, color, and placement."}`;79 `jobs_wait`, then `asset_display`.8081## Common mistakes8283- Carrying one editor's source field to the other: `referenceImages` (array of exactly one) and84 `image` (single file) are member-specific shapes.85- Leaving in-image copy unquoted: only quoted text renders verbatim.86- Stacking several edits in one instruction: one change per pass, then chain.87- Sending pixel sizes or a ratio the member lacks: `aspectRatio` is an enum and the lists differ88 (21:9, 5:4, and 4:5 lived on one member at authoring time).89- Re-running for a pixel-identical result: no seed exists; keep the winning asset and edit it90 forward.91- Shipping the 1K output to print: upscale downstream (see the `scenario-image` skill).