Reference reviewed September 18, 2026. Capabilities can change with your installed TimeBolt version.
Reading
| Tool | Input | Documented purpose |
get_file_path | {} | Read the open media path |
get_duration | {} | Read duration; observed source duration, not kept-output duration |
get_timeline | {} | Read existing timeline before editing |
get_umcheck_transcription | {} | Read prepared word-level transcript; if empty, prepare it in TimeBolt or supply a transcript |
get_predefined_filler_words_and_phrases | {} | Read predefined comma-separated filler list |
get_render_queue | {} | Read remaining rendering tasks |
Opening and writing
open_file_in_timeline: input { "filePath": "/absolute/path/to/video.mp4" }. Opens new media; not a way to import transcription JSON.
apply_timeline outer input schema:
{
"type": "object",
"properties": { "timeline": { "type": "string" } },
"required": ["timeline"]
}
The timeline string contains a serialized JSON array, not a raw array argument. The server description gives these inner constraints:
| Field | Contract supplied in description |
start, duration | Source interval coordinates; inspected values use seconds |
type | keep, remove, fastforward |
punched | At least 1, strictly less than 5 |
punchedPosition | center, top-left, top-right, bottom-left, bottom-right, top, bottom, left, right |
operation | Field is named, but its allowed values are not specified in the exposed description; inspected keep/remove regions mirror type |
marked | Boolean |
title | String; identifies the start/title of a chapter or topic |
Read and modify the existing timeline; do not discard prior edits. The description requires no gaps, with uncovered gaps explicitly represented as remove regions. The description does not provide a formal inner JSON Schema, a maximum payload size, overlap policy, fast-forward speed semantics, or error/return schemas. Do not pretend those are established.
Illustrative whole timeline for a fictional 3-second source, not an instruction to overwrite the current project:
{
"timeline": "[{\"start\":0,\"duration\":1,\"type\":\"keep\",\"punched\":1,\"punchedPosition\":\"center\",\"operation\":\"keep\",\"marked\":false,\"title\":\"\"},{\"start\":1,\"duration\":2,\"type\":\"remove\",\"punched\":1,\"punchedPosition\":\"center\",\"operation\":\"remove\",\"marked\":false,\"title\":\"\"}]"
}
Rendering and export
All tools below take an empty object in the documented usage.
add_to_render_queue: queue the current timeline.start_render: start all queued tasks; check the queue before invoking it.generate_fcpxml: generate Final Cut Pro XML; save it and return its path.generate_fcpxml_multicam: generate multicam FCPXML.generate_xml: generate XML for Premiere Pro / DaVinci Resolve.generate_xml_sequence: generate nested-sequence XML for Premiere Pro.generate_srt: generate a caption file from timeline/transcription.
The exposed tools do not configure render format, Turbo, vertical crop or aspect ratio, start UMCheck, or import an existing UMCheck JSON by path. Exporting FCPXML does not itself prove boundary correction.
Configuration
Current supported customer instructions: Claude Desktop setup. The application provides a connection command. Manual configuration JSON is not established by this tool listing. Add platform-specific, tested JSON and a Copy action only after the connector maintainer supplies it. Never invent a localhost port or executable path.
Proposed adjacent documentation: /docs/mcp/known-behaviors. Both paths are planned, not currently verified public pages.
Known behaviors →
