Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

delete_keyframe

Removes animation keyframes from Blender object location, rotation, or scale channels at a specified frame, with optional axis targeting and channel-bound validation.

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": "delete_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?

With no annotations, the description carries the full behavioral burden and does not meet it. It does not say whether deletes are reversible, what happens to existing keyframes or curves, whether the operation requires a specific mode (pose mode is only hinted at via bone_name), or what 'verified channel bounds' actually means.

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?

It is a single, front-loaded sentence with no padding. The only structural weakness is that the three-verb opening blurs the tool's identity rather than sharpening it.

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 an unannotated mutation tool with nine parameters and no output schema, yet the description says nothing about destructive effects, the untrusted 'approved' flag, task_id scoping, or bone_name usage. Far more disclosure is needed for an agent to invoke it safely.

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 every parameter is already documented, including the index axis mapping and the action enum. The description only restates the property values and frame targeting, adding no meaning beyond the schema.

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 description names a concrete resource (animation keyframes) and the supported properties, but it opens with 'Inserts, updates, or deletes,' which conflicts with the tool name delete_keyframe and with siblings like insert_keyframe and manage_keyframe. An agent cannot tell from this text why it should pick this tool over those siblings for an insert.

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 statement of when to use this tool versus insert_keyframe or manage_keyframe, and no prerequisites or exclusions are given. The only implicit guidance is the 'action' enum, which is a schema detail rather than usage guidance.

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