Skip to main content
Glama

set_keyframe

Sets a property value and keyframes it at a chosen frame, letting AI clients animate Blender objects and settings through MCP.

Instructions

Set a property value and keyframe it.

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>",
      "value": "<value>"
    },
    "name": "set_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
frameNo
valueYes
data_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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 burden, and it discloses almost nothing: it does not say whether an existing keyframe at that frame is overwritten, whether the property must already be animated, what permissions or object context are required, or what the response contains. Only the bare implication of inserting a keyframe at a frame is conveyed.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, but its brevity is under-specification rather than disciplined conciseness. Nothing is wasted, yet almost nothing is delivered.

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?

For a four-parameter mutation tool with no annotations and no schema descriptions, the one-line description is well short of what an agent needs to call it safely and correctly. An output schema exists, so return values need not be explained, but that does not offset the missing input and behavioral context.

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 four parameters, and the description adds no meaning beyond the schema — it does not explain what 'name' identifies, what path format 'data_path' expects, how 'frame' defaults (null), or what types 'value' accepts. This is the weakest area of the definition.

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 specific action (set a value and keyframe it), which is more than a tautology, but it never says what 'name' or 'data_path' refer to, so the resource being modified is vague. It also gives no hint of how it differs from close siblings like create_keyframe or the various set_* property tools.

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 such as create_keyframe or remove_keyframe. The agent must infer everything about when this tool is the right choice from the 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