Insert animation keyframes on Blender objects by defining data paths (location, rotation, scale, custom properties), optional values, and frame numbers to control property changes over time.
插关键帧。data_path 如 location / rotation_euler / scale / hide_render / ["prop"]；给 value 先赋值再打帧；index 指定分量。
| Name | Required | Description | Default |
|---|---|---|---|
| frame | No | ||
| index | No | ||
| value | No | ||
| object | Yes | ||
| data_path | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Mentions that value should be assigned before keyframing, but does not disclose side effects, error handling, or behavior with null frame/object.
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?
Short and dense, includes examples without fluff.
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?
Sufficient for a simple tool, but lacks details on all parameters and error cases. Does not mention interaction with animation timeline or batch operations.
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?
Description explains data_path, value, and index semantics, but omits frame and object meaning. Schema has no descriptions, so partial compensation.
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?
States it inserts a keyframe with concrete examples of data_path and usage notes on value and index. Clearly distinguishes from batch insertion via name.
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?
Provides usage tips (assign value first, index for component) but does not explicitly contrast with alternative tools like insert_keyframes_batch or delete_keyframe.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.