Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_davinci_sync

Synchronize project timelines, shots, and audio with DaVinci Resolve or export FCPXML 1.10, and install the round-trip edit action script for clip editing in ComfyUI.

Instructions

Synchronize project timeline, shots, and audio directly with DaVinci Resolve (or export FCPXML 1.10). Automatically installs the 'CineFlow: Edit in ComfyUI' action script for round-trip clip editing.

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": {
      "project_id": "<project_id>"
    },
    "name": "cineflow_davinci_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesTarget project ID.
timeline_nameNoCustom timeline name in DaVinci Resolve.
install_actionNoWhether to install CineFlow_Edit_in_ComfyUI script in Resolve Edit menu.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With zero annotations the description carries the full burden, and it does disclose a meaningful side effect: it installs the 'CineFlow: Edit in ComfyUI' script into the Resolve Edit menu, which mutates state outside CineFlow. However, it omits whether existing timelines are overwritten, what happens if Resolve is not running, and whether the install is unconditional ('automatically installs') or gated by the install_action parameter, which reads as a toggle.

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?

Two sentences with no filler, and the core sync capability is front-loaded before the side-effect note. The compressed '(or export FCPXML 1.10)' clause trades clarity for brevity by presenting an alternative mode without any indication of how to request it.

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 three-parameter integration tool with no annotations and no output schema, the definition covers the what and one side effect but leaves out prerequisites, mutation semantics against existing Resolve timelines, and the mechanics of the export path. The missing link between the advertised FCPXML export and any input parameter is a real completeness gap.

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 description coverage is 100%, so all three parameters are already documented and the baseline is 3. The description adds no syntax, default, or behavioral detail for project_id, timeline_name, or install_action, and notably never explains how the FCPXML-export alternative is invoked even though no parameter appears to select it.

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 verb and resource set (synchronize project timeline, shots, and audio) plus the concrete target application, DaVinci Resolve. The parenthetical '(or export FCPXML 1.10)' introduces a second mode without explaining how it is selected, which keeps the primary action slightly ambiguous, but no sibling tool competes for this purpose.

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?

There is no explicit when-to-use guidance, no prerequisites (e.g., Resolve must be installed and running), and no routing to alternatives such as cineflow_export_mp4. The round-trip editing phrase hints at context but leaves the agent to infer the trigger conditions.

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