Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

insert_keyframe

Inserts, updates, or deletes animation keyframes for Blender object location, rotation, and scale at specified frames, with verified channel bounds and optional axis targeting.

Instructions

Inserts, updates, or deletes animation keyframes for supported object properties (location, rotation_euler, scale) at specified frames with verified channel bounds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "property_path": "<property_path>",
      "frame": "<frame>"
    },
    "name": "insert_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTarget object name.
frameYesFrame number for keyframe insertion/deletion.
indexNoArray index for multi-axis properties: -1 for all axes, or 0 (X), 1 (Y), 2 (Z). Defaults to -1.
valueNoOptional numeric value or 3-element array to set prior to inserting the keyframe.
actionNoOperation to perform: 'insert' (default) or 'delete'.insert
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
bone_nameNoOptional pose bone name if keyframing an armature bone in pose mode.
property_pathYesProperty to keyframe: 'location', 'rotation_euler', or 'scale'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the three mutation modes and adds a mild behavioral claim about 'verified channel bounds', but it never says whether existing keyframes at a frame are overwritten, whether delete is reversible, what permissions or modes are required, or what the call returns.

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?

A single front-loaded sentence covering the verb set, the resource, the supported properties, and the frame anchoring; nothing is wasted. It is slightly dense and the 'verified channel bounds' clause is unexplained, but the structure is efficient.

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?

For a 9-parameter mutation tool with no annotations and no output schema, the description covers the core operation but omits the insert-vs-update-vs-delete semantics, mode requirements, and the effect of bone_name and task_id. It is minimally adequate rather than complete.

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 description coverage is 100%, so the schema already documents all nine parameters, including the index mapping and the approved-flag deprecation notice. The description only restates the supported property path values, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb set (inserts, updates, deletes) and resource (animation keyframes) and names the supported properties, so an agent knows the domain precisely. It stops short of distinguishing itself from the sibling delete_keyframe or explaining how the update case relates to insert, which keeps it below a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over delete_keyframe or manage_keyframe, and no preconditions (object mode vs pose mode, existing animation data) are stated. The action enum implies insert vs delete, but the description never addresses the sibling overlap it creates.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools