Skip to main content
Glama

remove_keyframe

Deletes a keyframe from a Blender animation data path, optionally at a specified frame, to remove unwanted animation keys.

Instructions

Remove a keyframe.

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>",
      "data_path": "<data_path>"
    },
    "name": "remove_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
frameNo
data_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it reveals nothing about what is destroyed (all channels vs one channel), whether the deletion is undoable, or what happens when frame is null. Only the word "Remove" hints at a destructive mutation, and that is inferred from the name rather than the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but this is under-specification rather than conciseness; it saves words by omitting all operative detail. There is no structure or front-loading to speak of because there is only one clause.

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

Completeness1/5

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

An output schema exists, so return values need not be explained, but for a three-parameter destructive tool with zero schema coverage the description supplies no targeting semantics, no behavioral guarantees, and no usage conditions. An agent would have to guess how to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters (name, data_path, frame, with frame defaulting to null), and the description names none of them. The critical semantics of an optional frame argument — whether null removes the keyframe across all frames or targets a default frame — are completely undocumented.

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 states a concrete verb and resource ("Remove a keyframe"), so an agent can tell it is a mutation on keyframe data rather than a read or an animation setter. It does not distinguish itself from siblings such as set_keyframe or create_keyframe, nor does it say what a keyframe is attached to (the data_path target).

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, no prerequisites, and no mention of alternatives in the sibling catalog (e.g. set_keyframe for editing rather than deleting). The agent must infer usage entirely from the tool name.

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