Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_vse_timeline

Inspect Blender's Video Sequence Editor timeline to retrieve frame range, FPS, occupied channels, strip descriptors, and markers, so you can audit scene timing and structure before editing.

Instructions

Inspect the Video Sequence Editor (VSE) timeline: frame range, FPS, occupied channels, summary descriptors of all strips, and timeline markers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_vse_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_stripsNoWhether to include detailed strip descriptors (default True).
include_markersNoWhether to include timeline markers (default True).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden. It does disclose the shape of what is returned (frame range, FPS, channels, strips, markers) and that strips/markers are optional, which is useful, but it never states that the tool is non-mutating, what happens when no VSE exists or the timeline is empty, or whether large strip counts are truncated.

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

Conciseness5/5

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

A single front-loaded sentence that names the resource first and then lists the returned facets in a compact enumeration. No redundant or filler wording; every clause conveys content the agent needs.

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

Completeness4/5

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

For a no-annotation read tool with a fully documented two-parameter schema and no output schema, the description adequately covers what the call yields. The remaining gap is edge-case behavior (empty timeline, absent VSE), which is minor for an inspection tool of this simplicity.

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 100%, so both boolean flags are already documented with defaults in the schema, establishing the baseline of 3. The description adds only loose mapping wording ('summary descriptors of all strips', 'timeline markers') without extra semantics such as the cost of disabling them or what a descriptor contains.

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 ('Inspect') plus the exact resource ('Video Sequence Editor (VSE) timeline') and enumerates the returned facets: frame range, FPS, occupied channels, strip descriptors, and markers. An agent can distinguish this from VSE mutation siblings like create_vse_strip or delete_vse_strip, though it does not contrast with read siblings such as inspect_scene_data.

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 by the word 'Inspect' and the VSE scope; there is no explicit statement of when to prefer this over other inspect_* tools (e.g. whether scene-level FPS/frame-range should come from inspect_scene_data). No exclusions or preconditions are stated, leaving routing to the agent's inference.

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