Skip to main content
Glama

delete_object_animations

Remove animations from an object. Use optional filters to delete specific animation types, groups, or directions; omit all to clear every animation.

Instructions

Delete animations from an object. Omit all optional filters to delete every animation; pass animation_type and/or animation_group_id (both shown by get_object) 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
object_idYesObject ID
animation_typeNoAnimation type shown by get_object (e.g. 'walk', 'idle')
animation_group_idNoAnimation group UUID shown by get_object as [group: ...]
Behavior3/5

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

No annotations exist, so description carries full burden. It describes deletion behavior with filtering but does not disclose whether it's destructive, reversible, or requires permissions. The deletion nature is implied but not detailed beyond the action.

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 sentences, front-loaded, no filler. Every word serves a purpose.

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?

With 4 params (1 required) and no output schema, the description sufficiently covers all parameters and usage patterns, leaving no ambiguity for an AI agent.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds value by explaining how filters work together and references get_object for obtaining values, which is not in the schema.

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 'Delete animations from an object' with a specific verb and resource. It distinguishes from sibling tools like delete_character_animations and delete_object.

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

Usage Guidelines4/5

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

Provides explicit guidance on when to use each optional filter: 'Omit all optional filters to delete every animation; pass animation_type and/or animation_group_id to narrow it, and direction to remove a single direction only.' Does not state when not to use, but context is clear.

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