Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

manage_timeline_markers

Add, remove, or list timeline markers in the active Blender scene to organize animation events by marker name and frame.

Instructions

Manage timeline markers in the active scene: add, remove, or list markers.

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": {
      "action": "<action>"
    },
    "name": "manage_timeline_markers"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoMarker name (required for 'add' and 'remove').
frameNoTimeline frame index for the marker (required for 'add').
actionYesMarker operation to perform.
task_idNo
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
request_idNo
approval_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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. It never states whether markers persist to the scene file, whether removal is reversible/undoable, what happens when removing a non-existent marker, what 'list' returns, or what the approval_token/approved parameters gate. For a mutating tool with zero annotation coverage this is a significant gap.

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 zero filler, and the resource is stated before the operations. It is efficient but leaves available space unused for the behavioral detail this tool needs.

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?

With 7 parameters, no output schema, and no annotations, the one-sentence description is far too thin. An agent cannot predict mutation side effects, return shape, or how the approval-related parameters affect the call, all of which must come from the description in this tool's case.

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

Parameters2/5

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

Schema coverage is only 57% across 7 parameters, and the description adds essentially nothing beyond the enum already in the schema: it never explains the frame index semantics, nor does it mention what task_id, request_id, approval_token, or approved do (the 'approved' description itself is a deprecation warning rather than semantic help).

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?

Names a specific resource ('timeline markers in the active scene') and enumerates the three supported verbs (add, remove, list), so an agent can tell it apart from siblings like manage_keyframe or inspect_vse_timeline. It stops short of explicitly contrasting itself with a sibling, which keeps it at 4.

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?

The action list describes what operations exist, not when to choose this tool over alternatives such as inspect_vse_timeline for reading timeline state. No prerequisites, no exclusions, and no guidance on picking 'list' versus inspecting the timeline another way.

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