Aseprite MCP

Overview Schema Source Related Servers Discussions Admin

fill_layer

Destructive

Fill an entire layer or frame cel with a solid color. Provide filename, color, and optional frame or layer to apply flat fills in Aseprite MCP.

Instructions

Fill the entire target layer/frame cel with a solid colour.

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>",
      "color": "<color>"
    },
    "name": "fill_layer"
  }
}

Input Schema

Name	Required	Description
`color`	Yes
`frame`	No	Default: 1.
`layer`	No
`filename`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.10.0Oct 4, 2026
- removedInput schema / properties / color / title
```
Removed value: -"Color"
```
- 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 / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / layer / default
```
Removed value: -null
```
- removedInput schema / properties / layer / title
```
Removed value: -"Layer"
```
- addedInput schema / properties / layer / type
```
Added value: +"string"
```
- removedInput schema / title
```
Removed value: -"fill_layerArguments"
```
First observedv0.7.0Jul 29, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description contributes the fact that the WHOLE layer/cel is overwritten with a single colour, which corroborates destructiveness, but says nothing about whether the file is saved, whether existing pixels are irrecoverably lost, or what is returned. Adequate but thin given the mutation/destructive nature.

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?

A single sentence with no filler, front-loading the verb and scope. Nothing to trim.

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 destructive mutation with no output schema, 4 parameters at 25% description coverage, and many sibling fill/clear tools, the description is too spare. It omits save semantics, colour format, error cases, and any disambiguation from adjacent fill/clear operations.

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 coverage is only 25% and the description adds little: it signals that layer, frame, and color are involved but gives no colour format (hex? named? alpha?), no explanation of which cel on the layer/frame is targeted, and says nothing about the required filename parameter. Low coverage means the description should compensate more than it does.

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 pairs a specific verb ("Fill") with a clear resource ("the entire target layer/frame cel") and the fill material ("solid colour"). It is distinguishable from fill_area (region) and fill_gradient/checkerboard, though it never names those siblings explicitly.

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?

There is no guidance on when to choose this over fill_area, clear_layer, or fill_tile, nor any prerequisite (e.g., layer must exist, file must be loaded). Usage must be inferred from the word "entire".

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

Deploy Server