Aseprite-MCP

Overview Schema Source Related Servers Discussions Admin

export_layer_only

Export a specific layer from an Aseprite file as a flattened PNG. Use this to isolate individual layers for focused output.

Instructions

Exports only the specified layer to a flattened PNG

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": {
      "layerName": "<layerName>",
      "outputDir": "<outputDir>",
      "inputFile": "<inputFile>"
    },
    "name": "export_layer_only"
  }
}

Input Schema

Name	Required	Description	Default
`inputFile`	Yes
`layerName`	Yes
`outputDir`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 5, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as side effects, permissions, error handling, or whether files are overwritten.

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?

The description is a single concise sentence that conveys the core purpose without any wasted words.

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

Completeness2/5

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

Given the lack of output schema and 0% parameter coverage, the description is too minimal; it omits critical details like file overwrite behavior, resolution, and error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description adds no meaning to the three parameters (inputFile, layerName, outputDir), leaving their formatting and constraints entirely unclear.

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?

The description clearly states the tool exports a specified layer to a flattened PNG, using a specific verb and resource, distinguishing it from sibling tools like export_sheet or export_frames.

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?

The description implies usage for exporting a single layer, but does not explicitly provide when to use it over alternatives like export_sheet or merge_visible_layers.

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