Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

delete_tag

Destructive

Delete an animation tag by name from an Aseprite file. Removes unwanted tags to keep sprite animations organized and export-ready.

Instructions

Delete the animation tag named name.

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": {
      "name": "<name>"
    },
    "name": "delete_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

The destructiveHint=true annotation already declares this is a destructive operation, and the description's 'Delete' is consistent with it. However, the description adds nothing beyond that: it doesn't say whether the deletion is reversible, whether tagged frames are affected, or whether the operation scopes to the whole file — all meaningful context for an irreversible mutation.

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?

A single short sentence with the resource and target front-loaded and no wasted words. The RST-style double-backtick markup around 'name' is slightly awkward but doesn't harm parsing.

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 and zero schema coverage on two parameters, this one-line description is too thin. It leaves unresolved what happens to frames under the tag, whether the action is undoable, and what the 'file' argument selects.

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 0%, so the description bears full responsibility for parameter meaning. It only clarifies that 'name' is the animation tag's name; the 'file' parameter (nullable, default null) is completely unexplained, leaving the caller to guess which document is modified.

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 states a specific verb ('Delete') and resource ('the animation tag'), and identifies the target by name. This distinguishes it from sibling deletion tools like delete_frame, delete_layer, and delete_slice, though it never names those alternatives 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 use this tool versus rename_tag, create_tag, or the other delete_* siblings, and no stated prerequisites. The agent must infer everything about selection from the tool name alone.

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

Deploy Server

Other Tools