aseprite-ai-artist

Overview Schema Source Related Servers Discussions Admin

Export

export

Destructive

Write game-ready PNG, GIF, spritesheet with JSON atlas, or numbered frames from Aseprite sprites, so game engines can load them directly.

Instructions

Write game-ready files. Ops: 'png' (single frame), 'gif' (animation), 'spritesheet' (packed sheet plus a JSON atlas with per-frame and per-tag data), 'frames' (numbered PNGs), 'aseprite' (save a copy of the source). Spritesheet is what an engine actually consumes: pass sheetType and byTag to control layout. Exporting does not save the working document — use sprite_manage op 'save' for that.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`op`	Yes
`path`	Yes	Output file path. For 'frames', a pattern containing {frame}, e.g. 'walk_{frame}.png' — Aseprite expands it into one file per frame, numbered from 0.
`tags`	No	Export only the frames these tags cover. gif, frames, spritesheet; 'png' and 'aseprite' refuse it. An unknown tag is refused.
`trim`	No	Trim transparent margins; the atlas keeps the original offsets.
`byTag`	No	Split the sheet by animation tag.
`frame`	No	1-based frame number. Omit to use the active frame.
`scale`	No	Integer upscale, nearest-neighbour.
`layers`	No	Export only these layers (names or group paths; a group brings its children). png, gif, frames, spritesheet; 'aseprite' refuses it.
`sprite`	No	Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused.
`padding`	No	Pixels between frames; prevents bleed at non-integer zoom.
`sheetType`	No	Spritesheet layout.	horizontal
`includeJson`	No	Write a sibling JSON atlas for 'spritesheet'.

Output Schema

TableJSON Schema

Name	Required	Description
`op`	Yes
`atlas`	No
`files`	Yes
`frame`	No	Which frame a single-frame export wrote. Defaults to the active frame, which is not always the one you drew on.
`width`	No
`height`	No
`sprite`	Yes
`frameCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.0Oct 2, 2026

changedInput schema / properties / layers / description

Previous value: -"Export only these layers."New value: +"Export only these layers (names or group paths; a group brings its children). png, gif, frames, spritesheet; 'aseprite' refuses it."

changedInput schema / properties / tags / description

Previous value: -"Export only these tags."New value: +"Export only the frames these tags cover. gif, frames, spritesheet; 'png' and 'aseprite' refuse it. An unknown tag is refused."

Changed2 schema fields changedv0.1.6Sep 9, 2026

changedInput schema / properties / path / description

Previous value: -"Output file path. For 'frames', a pattern like 'walk_{frame}.png'."New value: +"Output file path. For 'frames', a pattern containing {frame}, e.g. 'walk_{frame}.png' — Aseprite expands it into one file per frame, numbered from 0."

changedInput schema / properties / sprite / description

Previous value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."

First observedv0.1.0Sep 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With destructiveHint=true already declared, the description adds real context: it discloses that export writes to disk but leaves the working document untouched, that the atlas preserves original offsets when trimmed, and that per-op option combinations are accepted or refused. It does not address overwrite behavior for an existing path, which is the one remaining destructive concern.

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?

Four dense sentences, front-loaded with the action, then op enumeration, then the spritesheet recommendation, then the save-tool caveat. No filler and no repetition of schema content.

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 output schema covers return shapes, so covering them is unnecessary, and the description handles op semantics and the save distinction well. The only gap is that the destructive hint is left to the annotation without the description clarifying that an existing file at `path` may be overwritten.

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 92%, so nearly every parameter is already documented in the schema (including trim offsets, frames pattern expansion, tags/layers per-op refusal). The description only repeats sheetType and byTag as the layout controls, adding no syntax beyond the schema. Baseline 3 is correct.

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 ('Write game-ready files') and then enumerates exactly what the five ops produce, including the artifacts (JSON atlas with per-frame and per-tag data, numbered PNGs, source copy). An agent can distinguish this from look/draw/sprite_manage 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 Guidelines5/5

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

Explicitly routes the agent: 'Exporting does not save the working document — use sprite_manage op save for that,' and names the condition that selects the default op ('Spritesheet is what an engine actually consumes'). The when-to-use and the alternative are both stated, not implied.

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

Deploy Server