aseprite-ai-artist

Overview Schema Source Related Servers Discussions Admin

Frames

frame

Destructive

Manage animation sequence: list, add, duplicate, delete, reorder, or activate cels and set per-cel millisecond durations. Use count and durations to build or retime a full cycle.

Instructions

Manage animation frames. Ops: 'list', 'add', 'duplicate', 'delete', 'set_duration', 'activate', 'reorder'. Durations are milliseconds per frame and carry most of the life in a cycle — hold a contact pose longer than a pass pose. Use count to add several at once and durations to set a whole cycle's timing in one call.

Input Schema

TableJSON Schema

Name	Required	Description
`op`	Yes
`count`	No
`frame`	No	1-based frame number. Omit to use the active frame.
`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.
`toIndex`	No	For 'reorder': the 1-based position `frame` ends up at. Its cels and duration move with it; tag ranges stay where they are.
`linkCels`	No	For 'duplicate': share the cel image instead of copying it, so edits apply to both.
`durations`	No	Per-frame durations from frame 1, for 'set_duration'.
`afterFrame`	No	Insert position. Default: at the end.
`durationMs`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`frames`	No
`sprite`	Yes
`frameCount`	Yes
`activeFrame`	No
`totalDurationMs`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.0Oct 2, 2026

changedInput schema / properties / toIndex / description

Previous value: -"For 'reorder'."New value: +"For 'reorder': the 1-based position `frame` ends up at. Its cels and duration move with it; tag ranges stay where they are."

Changed1 schema field changedv0.1.6Sep 9, 2026

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

A3.6/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds domain context about duration semantics but never says which specific ops are destructive/irreversible (delete) or what happens to existing frames on reorder — a meaningful gap for a multiplexed mutation tool. No contradiction 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then ops, then parameter hints — a sensible order with no repetition. The artistic aside ('hold a contact pose longer than a pass pose') is mildly extraneous but small, and the rest of the text is tight.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a 7-op multiplexed tool with one required param, the description is close to complete; the residual gap is that it does not map parameters to ops or flag which ops are irreversible.

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 67%, and the description compensates by clarifying that durations are 'milliseconds per frame' (not stated in the durations schema description) and that `count` batches adds and `durations` sets a whole cycle in one call. This adds real operational meaning beyond the schema for the two least self-explanatory parameters.

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?

The description states a clear resource ('animation frames') and enumerates the seven concrete operations, so an agent knows exactly what this tool covers. 'Manage' is somewhat generic as a verb, and no sibling (e.g. cel, tag, layer) is named for disambiguation, but the op list makes the scope unambiguous.

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?

Listing the ops implies when each is used, and the closing sentence says to use `count` for bulk adds and `durations` for whole-cycle timing. However, there is no explicit when-to-use versus sibling tools (cel/tag/layer), no prerequisites, and no guidance on which ops are destructive or when to prefer 'duplicate' with linkCels.

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

Deploy Server