Skip to main content
Glama

delete_character_animations

Remove character animations by type, group, or direction. Omit optional filters to delete all animations.

Instructions

Delete animations from a character. Omit all optional filters to delete every animation; pass animation_type and/or animation_group_id (both shown by get_character) to narrow it, and direction to remove a single direction only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directionNoSingle direction to delete (e.g. 'south'). Omit for all directions
character_idYesCharacter ID
animation_typeNoAnimation type shown by get_character (e.g. 'walk', 'idle')
animation_group_idNoAnimation group UUID shown by get_character as [group: ...]
Behavior4/5

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

No annotations provided, so description bears full burden. It discloses that omitting all filters deletes every animation on the character, which is important destructive behavior. It explains the effect of each filter, but could mention if deletion is irreversible.

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?

Two concise sentences: first states purpose, second explains usage variants. No unnecessary words, front-loaded with key action.

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

Completeness5/5

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

For a tool with 4 params (1 required) and no output schema, the description comprehensively covers behavior for all usage scenarios (delete all vs. selective with filters). No ambiguity.

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

Parameters5/5

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

Schema coverage is 100%, but description adds value by explaining how parameters interact (omitting all deletes all, using filters narrows) and referencing get_character as the source for animation_type and animation_group_id.

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 action (Delete) and resource (animations from a character). It differentiates from siblings like delete_character or delete_object_animations by detailing how to narrow deletion using specific filters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains when to delete all animations (omit optional filters) versus selectively delete by animation_type, animation_group_id, or direction. Provides clear guidance on how to narrow the operation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rabbitcannon/pixellab-forge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server