Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_export_mp4

Stitch rendered video clips, dialogue, and background music into a final MP4 timeline export, with optional music ducking under dialogue.

Instructions

Stitch rendered video clips, dialogue tracks, and background music into the final exported MP4 timeline.

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_export_mp4"
  }
}

Input Schema

NameRequiredDescriptionDefault
duckNoWhether to duck music volume under dialogue.
music_pathNoOptional background music audio file path.
project_idYesTarget project ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 behavioral burden, and it discloses almost nothing beyond the transformation itself. It does not say where the MP4 is written, whether an existing export is overwritten, whether the call blocks for a long render, or what happens if clips or music are missing — all critical for a write/export operation with zero annotation coverage.

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 no filler, and the outcome ('final exported MP4 timeline') lands immediately. It is efficient, though the terseness is part of why behavior and prerequisites go unstated.

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?

For an export/mutation tool with no annotations and no output schema, the description should cover the destination of the artifact, overwrite semantics, and expected duration or blocking behavior. None of that is present, so an agent knows what the tool does but not what it will produce or cost.

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 only marginal meaning — it implies video clips and dialogue are pulled from the project rather than passed as parameters, and 'background music' loosely maps to music_path — but the ducking flag is never mentioned in prose.

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?

States a specific verb and resource: 'Stitch ... into the final exported MP4 timeline', naming the three input ingredients (clips, dialogue, music). An agent can distinguish this terminal export step from generative siblings like cineflow_frames_generate or cineflow_dialogue_tts, though no sibling is named as an alternative.

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?

The word 'final' implies this is the last step after rendering and dialogue generation, which gives implied sequencing. However, there is no explicit when-to-use versus when-not-to-use guidance, no statement of prerequisites (rendered clips must already exist), and no mention of any alternative export path.

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