export_slice_metadata
Destructive
Exports Aseprite slices to engine-agnostic JSON, including bounds, pivot, nine-slice, color, and parsed user data, so game engines can consume sprite metadata.
Instructions
Export every slice as engine-agnostic JSON (aseprite_mcp.slice_metadata.v1).
Each slice becomes ``{name, type, id, bounds, pivot, nine_slice, color, data,
raw_data}``. **Type detection:** a slice's user-data JSON ``type`` wins; otherwise the
name convention ``<type>:<id>`` (recognized types: hitbox, hurtbox, collision, interact,
pivot, origin, attach, spawn, nine_slice; anything else becomes ``"custom"``, never an
error). ``id`` comes from the data ``id`` or the name's ``:<id>`` suffix. ``nine_slice``
(Aseprite's 9-patch center) and ``pivot`` are emitted whenever the slice has them. Slice
user-data that is valid JSON is parsed into ``data``; the raw string is kept in ``raw_data``.
Args:
output: Destination .json path. Defaults to ``<sprite>_slices.json`` beside the sprite.
overwrite: Replace an existing file (default False = no-clobber).
Returns a ``workflow_manifest.v1`` manifest (kind ``engine_metadata``).
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>"
},
"name": "export_slice_metadata"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| output | No | ||
| filename | Yes | ||
| overwrite | No | Default: false. |