Aseprite MCP

Overview Schema Source Related Servers Discussions Admin

export_layer

Destructive

Export a single layer from a specific frame as a PNG, excluding other layers. Overwrite controls replacing existing output; default prevents overwriting.

Instructions

Export a single layer of one frame as a PNG (others excluded).

overwrite: Replace `output` if it already exists (default False = no-clobber).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filename": "<filename>",
      "layer": "<layer>",
      "output": "<output>"
    },
    "name": "export_layer"
  }
}

Input Schema

Name	Required	Description
`frame`	No	Default: 1.
`layer`	Yes
`scale`	No	Default: 1.
`output`	Yes
`filename`	Yes
`overwrite`	No	Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.10.0Oct 4, 2026
- removedInput schema / properties / filename / title
```
Removed value: -"Filename"
```
- addedInput schema / properties / frame / description
```
Added value: +"Default: 1."
```
- removedInput schema / properties / frame / title
```
Removed value: -"Frame"
```
- removedInput schema / properties / layer / title
```
Removed value: -"Layer"
```
- removedInput schema / properties / output / title
```
Removed value: -"Output"
```
- addedInput schema / properties / overwrite
```
Added value: +{
+  "default": false,
+  "description": "Default: false.",
+  "type": "boolean"
+}
```
- addedInput schema / properties / scale / description
```
Added value: +"Default: 1."
```
- removedInput schema / properties / scale / title
```
Removed value: -"Scale"
```
- removedInput schema / title
```
Removed value: -"export_layerArguments"
```
First observedv0.7.0Jul 29, 2026

TDQS

B3.2/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, and the description adds useful non-clobber context: overwrite defaults to False so an existing `output` is preserved unless opted in. It does not, however, clarify whether the export writes files to disk, what happens on path conflicts beyond the overwrite flag, or any auth constraints.

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?

Two short lines, front-loaded with the purpose and followed by the one non-obvious parameter's behavior. No filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, six-parameter write tool with no output schema, the definition covers the core action and the overwrite semantics but is thin on the remaining parameters and on side effects. Adequate but with clear gaps.

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 50% and six parameters exist, so the schema does only part of the work. The description adds real meaning for `overwrite` (no-clobber default), but says nothing about `filename` vs `output`, `scale`, or `frame`, leaving half the parameters ambiguous.

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 (export), resource (single layer of one frame), format (PNG), and scope (others excluded), which meaningfully distinguishes it from export_png and export_layers. It stops short of naming those siblings explicitly, so an agent must infer the routing.

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 parenthetical 'others excluded' implies this is the narrow per-layer variant, but the description never says when to prefer it over export_png, export_layers, export_frames, or export_spritesheet. No prerequisites or alternatives are given.

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

Deploy Server