Skip to main content
Glama

blender_edit_animation

Destructive

Edit animation data by inserting, modifying, or deleting keyframes, managing NLA strips, setting drivers, and controlling shape keys and timeline settings.

Instructions

Edit animation data — insert/modify/delete keyframes, manage NLA strips, set drivers, control shape keys, and configure timeline settings.

Use this when: you need to create or modify animation.

Do NOT use for: reading animation data (use blender_get_animation_data).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe animation operation to perform.
object_nameNoTarget object name.
data_pathNoProperty path for keyframe/driver (e.g. 'location', 'rotation_euler', 'scale').
indexNoArray index for the property (-1 for all channels, 0/1/2 for X/Y/Z).
frameNoFrame number for keyframe operations.
valueNoValue for keyframe or shape key (number, array, or boolean).
interpolationNoKeyframe interpolation type.
nla_actionNoAction name for NLA strip operations.
nla_start_frameNoStart frame for NLA strip.
nla_strip_nameNoNLA strip name for modify/remove.
driver_expressionNoPython expression for driver.
shape_key_nameNoShape key name for set_shape_key.
fpsNoFrames per second (for set_frame_range).
frame_startNoStart frame (for set_frame_range or set_frame).
frame_endNoEnd frame (for set_frame_range).
Behavior4/5

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

Annotations destuctiveHint=true and readOnlyHint=false are reinforced by description mentioning insert/modify/delete. No contradiction, and description adds specifics about what gets modified.

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?

The description is very concise: two sentences with purpose and usage guidelines, no unnecessary words. Front-loaded with the main function.

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

Completeness3/5

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

Given the complexity of the tool (15 params, 11 actions), the description is adequate for orientation but lacks details on parameter dependencies, return values, or prerequisites. No output schema to compensate.

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 15 parameters with descriptions (100% coverage), so the description's lack of parameter detail is acceptable. No additional semantics beyond 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 it edits animation data with specific operations (keyframes, NLA strips, drivers, shape keys, timeline) and distinguishes from the sibling blender_get_animation_data for reading.

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 says 'Use this when: you need to create or modify animation' and 'Do NOT use for: reading animation data (use blender_get_animation_data)', providing clear usage context and an alternative.

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/ageless-h/blender-mcp'

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