anim_clear_all
Removes every keyframe, driver, and animation action from a selected object in Blender.
Instructions
Remove all animation data from an object.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| object_name | Yes |
Removes every keyframe, driver, and animation action from a selected object in Blender.
Remove all animation data from an object.
| Name | Required | Description | Default |
|---|---|---|---|
| object_name | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Although no annotations are provided, the description lacks detail about the operation's irreversibility, effects on other object data, or required permissions. For a destructive operation, more transparency is needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, appropriately brief. It is well-structured and front-loaded with the verb. However, it could be slightly expanded with usage context without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description fails to cover basic behavioral information such as whether the operation can be undone or if it affects animations on child objects. Minimal completeness for a simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not explain the 'object_name' parameter beyond its name. With 0% schema description coverage, the description adds no semantic meaning, making it hard for the agent to know what value to provide.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Remove' with the resource 'all animation data' from an object, clearly distinguishing it from sibling tools like 'anim_delete_keyframe' which targets specific frames.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as 'anim_delete_keyframe' or 'clear_animation'. No prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dwgx/blender-copilot'
If you have feedback or need assistance with the MCP directory API, please join our Discord server