aseprite-mcp

aseprite_erase

Erase a rectangular region on an Aseprite layer, making it transparent across one or all frames. Specify x, y, width and height to clear pixels.

Instructions

Erase a rectangular region (make it transparent) on a layer, across frames.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "aseprite_erase"
  }
}

Input Schema

Name	Required	Description
`x`	Yes
`y`	Yes
`layer`	No	Layer to erase from (default active/first layer).
`width`	Yes
`frames`	No	Frame indices (default: all frames).
`height`	Yes
`document`	No	Document to act on: a short name inside the art folder ("hero"), a relative path, or an absolute .aseprite path. Omit to use the active document.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 27, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It states the effect (makes the region transparent) and scope (layer, across frames), but omits whether the action is destructive, reversible, how it interacts with other layers, or what result is returned.

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 front-loaded sentence with no wasted words. It is appropriately sized for the operation it names.

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?

For a 7-parameter tool with no annotations, no output schema, and low schema description coverage, the description is too thin. It does not explain the coordinate system, defaults beyond what the schema partially covers, or expected return behavior, leaving gaps an agent would need to infer.

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

Parameters2/5

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

Schema description coverage is only 43%, so the description must compensate. It implies that x, y, width, and height define a rectangular region and mentions layer and frames, but it adds no coordinate-system, units, or detailed parameter meaning beyond that.

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 names a specific verb (erase) and resource (rectangular region on a layer, across frames), making the core operation clear. It does not explicitly differentiate from siblings such as aseprite_remove_frame or aseprite_fill_regions, but the resource scope is distinct enough for an agent to understand.

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 description gives no when-to-use guidance or alternatives. It implies the operation is for erasing pixels in a rectangle across frames, but an agent gets no help choosing this over sibling tools like aseprite_fill_regions or aseprite_replace_color.

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

Deploy Server