Skip to main content
Glama

animation_create

Create a new animation clip in an AnimationPlayer's default library. Specify duration, loop mode, and optionally overwrite existing clips.

Instructions

Create a new Animation clip inside an AnimationPlayer's default library.

After creating the clip, add tracks via animation_manage ops add_property_track / add_method_track / create_simple. Track node paths are stored relative to the AnimationPlayer's root_node (default: its parent), not to the scene root — see animation_manage preset ops for a forgiving target_path that accepts either form. If player_path doesn't resolve, an AnimationPlayer is auto-created at that path (parent must exist).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAnimation clip name (e.g. "idle", "pulse").
lengthYesDuration in seconds.
loop_modeNo"none" (default) | "linear" | "pingpong".none
overwriteNoReplace an existing animation with the same name.
session_idNoOptional Godot session to target. Empty = active session.
player_pathYesScene path to the AnimationPlayer node.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Discloses auto-creation of AnimationPlayer if player_path doesn't resolve, and explains track path relativity. Does not mention behavior on overwrite=false conflict or other failure modes, nor permissions or side effects.

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?

Five sentences, each adds value. Front-loaded purpose. Minor redundancy in referencing animation_manage twice, but overall efficient.

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

Completeness4/5

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

Covers creation step, next steps, path nuances, and auto-creation. Lacks details on overwrite behavior and return value, but output schema may address the latter. Adequate for a creation tool.

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

Parameters3/5

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

Schema covers all parameters with descriptions. Description adds context for player_path (auto-creation) and path relativity, but does not significantly enhance understanding of individual parameters beyond 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?

Clearly states it creates an Animation clip inside an AnimationPlayer's default library. References sibling tool animation_manage for next steps, distinguishing the tool's scope.

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 workflow: create clip first, then add tracks via animation_manage. Warns about node path conventions. Could explicitly 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/hi-godot/godot-ai'

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