Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

animate_vse_strip

Insert or delete keyframes on VSE strip transform, crop, opacity, or audio properties to animate changes over time in Blender.

Instructions

Insert or delete keyframes on strip transform, crop, opacity, or audio properties in the VSE.

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>",
      "action": "<action>",
      "property": "<property>",
      "frame": "<frame>"
    },
    "name": "animate_vse_strip"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target strip in the sequence editor.
frameYesTimeline frame index for the keyframe.
valueNoOptional value to apply to the property before keyframing (for INSERT_KEYFRAME).
actionYesAnimation action: INSERT_KEYFRAME or DELETE_KEYFRAME.
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
propertyYesProperty identifier to keyframe.
request_idNo
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.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 behavioral burden. It signals a mutation (insert/delete keyframes) but says nothing about whether keyframing replaces existing keys, what happens when deleting a non-existent keyframe or an unknown strip name, whether the change is reversible, or what the call returns. That is a substantial gap for a write tool with zero annotation coverage.

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; the action verb and the affected property domains come first. It could be marginally stronger by separating the two actions, but nothing is wasted.

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 purpose and property taxonomy but leaves behavior on failure, keyframe replacement semantics and the meaning of the bookkeeping parameters unaddressed. Adequate as a minimum-viable definition, incomplete for correct invocation in edge cases.

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 coverage is 67%, so the baseline is near 3. The description does add real meaning by grouping the opaque property enum values into transform, crop, opacity and audio categories, which helps an agent map intent to enum members. It adds nothing about frame semantics, the optional value pre-application, or the role of task_id/request_id/approval_token.

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 pair (insert/delete) plus the resource (keyframes) and scopes it to VSE strip transform, crop, opacity and audio properties. This is clearly distinguishable from siblings like transform_vse_strip or crop_vse_strip, which set values rather than animate them. It stops short of naming those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers this is the tool for time-based animation of strip properties rather than one-off value changes. There is no explicit guidance on when to prefer this over transform_vse_strip or crop_vse_strip, and no note about prerequisites such as the strip needing to exist.

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