video-harness
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doctorA | Diagnose Resolve connection (direct Studio scripting vs free-edition in-app bridge). |
| reconnectA | Drop the cached Resolve session and connect again. |
| inspectA | Snapshot of app, project, current timeline (tracks, items, markers), and media pool. media: 'current' (current bin) or 'all' (entire pool). |
| type_registry_getB | Marker type registry: id → color, scope (timeline|item|clip), duration (point|range). |
| media_importA | Import files into the current media pool folder. Returns media_id for each clip. |
| timeline_ensureB | Create the named timeline if needed and switch to it. Idempotent. |
| timeline_placeC | Place clips on the current timeline. Each item: media_id or clip_name or path; optional track_type, track_index, record_frame, source_in, source_out, media_type (1=video, 2=audio). |
| timeline_liftA | Delete timeline items by unique_id or by range. Effects on those items are lost. |
| timeline_assembleC | Ensure a timeline, optionally import media, and place clips. Rough cut in one call. |
| clip_set_colorA | Set Resolve clip color on timeline items (Orange, Green, Blue, …). Empty color clears. Match by unique_ids, media_id, or clip_name. If none given, colors every video/audio item. |
| marker_upsertA | Create or replace typed markers. Idempotent on payload.id. Each marker: type/name, frame, optional scope (timeline|item|clip), color, note, duration, unique_id (item), media_id (clip), payload {id, type, source, attrs}. If payload is omitted, pass type and id and the server will still store customData JSON if you include payload. Prefer markers_from_metadata for mapping. |
| markers_queryA | Query timeline, item, and clip markers. Filter by type, color, scope, frame range. |
| markers_from_metadataB | Map metadata events onto typed markers. Event: {type, at (timecode or frame), id?, duration_frames?, note?, scope?, media_id? or clip: {media_id, name, path}, attrs?, source?}. from_clips=true also stamps clip metadata fields (Keywords, Shot, …) as clip-scope markers. |
| markers_clearB | Delete markers by payload id, frame, or color. scope: timeline (default), item, clip. |
| clip_metadata_getC | Read built-in and third-party metadata for a media pool clip. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_status | Connection, product, version, page, project, timeline name. |
| resource_timeline | Full current-timeline inspect including tracks, items, and markers. |
| resource_types | Marker type registry. |
TDQS
Scored across 15 tools
Most tools target clearly distinct resources and actions, with clear prefixes for media, timeline, markers, and clips. The main overlap is between marker_upsert and markers_from_metadata, plus timeline_assemble combining functions that individual tools already provide, but descriptions make the intended use reasonably clear.
The dominant pattern is resource-first names like timeline_place and markers_query, which is predictable and readable. Minor inconsistencies exist: standalone verbs like reconnect, doctor, and inspect, plus singular/plural mixing between marker_upsert and markers_query/clear.
At 15 tools, the set stays within the well-scoped range and each tool serves a distinct purpose in the video editing workflow. The count feels appropriate for covering connection diagnostics, project inspection, media import, timeline assembly, clip styling, markers, and metadata without bloat.
The core lifecycle for building a rough cut is well covered: import media, ensure timelines, place/lift clips, set colors, and manage markers. However, there is no media deletion/rename, metadata write support, or render/export capability, so full end-to-end project management is not possible.