Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_keyframe

Insert, update, or delete Blender animation keyframes for location, rotation, or scale properties at specified frames, with optional axis, value, and pose-bone 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": "manage_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

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden for a mutation tool. The phrase 'with verified channel bounds' hints at validation but is undefined, and nothing states what data a delete destroys, whether keyframes are recoverable, what happens to existing interpolation, or what the call returns. The 'updates' claim also misdescribes the actual mutating actions.

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 with no filler, and the purpose plus property scope are stated immediately. It is efficient, though the compactness comes at the cost of the missing behavioral and routing detail noted elsewhere.

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

Completeness2/5

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

This is a nine-parameter mutation tool with no annotations and no output schema, so the description should explain delete semantics, the deprecated approved flag's trust implications, and the return shape. Instead it offers one sentence that only names the operation and properties, leaving destructive behavior and error/validation behavior ('verified channel bounds') unexplained.

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 baseline is 3 and the schema already explains name, frame, index, value, action, bone_name, and the deprecated approved flag. The description's only parameter-adjacent content restates the property_path enum values already in the schema and adds no semantics for value, index, or bone_name. It introduces a minor inconsistency by implying an update operation the schema does not support.

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

Purpose3/5

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

The verb+resource (insert/update/delete animation keyframes) is stated, and the supported properties are enumerated. However, the description claims it 'updates' keyframes while the schema's action enum only allows 'insert' and 'delete', so the stated scope is broader than reality. It also does not distinguish itself from the sibling tools delete_keyframe and insert_keyframe, which appear to cover subsets of this behavior.

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 when-to-use guidance at all: nothing says when to pick this consolidated tool versus the dedicated insert_keyframe or delete_keyframe siblings, and no prerequisites (e.g., object must be selected, must be in pose mode for bone_name) are given. The reader must infer routing from the tool name alone.

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