kinocut

Overview Schema Source Related Servers Discussions Admin

hyperframes_render

Render a Hyperframes project composition to video with control over output path, frame rate, resolution, quality, and format for shareable media.

Instructions

Render a Hyperframes composition to video.

Args: project_path: Absolute path to the Hyperframes project directory. output_path: Where to save the video. Auto-generated if omitted. fps: Frame rate (24, 30, 60). width: Output width in pixels. height: Output height in pixels. quality: Render quality (draft, standard, high). Default standard. format: Output format (mp4, webm, mov, png-sequence). Default mp4. resolution: Hyperframes resolution preset (landscape, portrait, landscape-4k, portrait-4k, 1080p, 4k, uhd). composition: Specific composition file to render instead of index.html. workers: Parallel render workers (number or 'auto'). Default auto. crf: Override encoder CRF (lower = better quality). variables: Inline JSON object/string with runtime data for the composition. variables_file: Path to a JSON file with runtime data for the composition.

Input Schema

Name	Required	Description
`crf`	No
`fps`	No
`gpu`	No
`hdr`	No
`sdr`	No
`quiet`	No
`width`	No
`docker`	No
`format`	No
`height`	No
`strict`	No
`quality`	No
`workers`	No
`overwrite`	No	Explicitly allow replacing existing media. Existing non-media files are protected.
`variables`	No
`resolution`	No
`strict_all`	No
`browser_gpu`	No
`composition`	No
`output_path`	No
`project_path`	Yes
`video_bitrate`	No
`no_browser_gpu`	No
`variables_file`	No
`strict_variables`	No
`max_concurrent_renders`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.16.4Oct 24, 2026

addedInput schema / properties / overwrite

Added value: +{
+  "default": false,
+  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
+  "title": "Overwrite",
+  "type": "boolean"
+}

Changed1 schema field changedv1.16.0Oct 3, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Addedv1.5.1Jun 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does not mention that this is a long-running/heavy operation, whether it overwrites existing output, what happens on failure, or any resource/permission considerations beyond the terse parameter list.

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?

Purpose is front-loaded in one line, followed by a compact per-parameter list where each line adds information not present in the schema. Slightly long, but with near-zero schema coverage the enumeration earns its space.

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?

An output schema exists, so return values do not need explanation, and the core render parameters are covered. However, for a 26-parameter mutation tool with no annotations, the missing behavioral profile and the undocumented half of the parameters leave clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 4%, so the description does real work: it documents 13 of 26 parameters with allowed values and defaults (fps 24/30/60, quality draft/standard/high, format mp4/webm/mov/png-sequence, resolution presets, workers 'auto', crf direction). It leaves roughly half undocumented (gpu, hdr, sdr, docker, strict*, quiet, video_bitrate, max_concurrent_renders), so it is not fully complete but clearly compensates for the barren schema.

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: 'Render a Hyperframes composition to video.' The 'Hyperframes composition' scoping differentiates it from revideo_render, though the description never explicitly contrasts with hyperframes_preview or hyperframes_still.

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 statement of when to use this tool versus sibling renderers/previewers like revideo_render, hyperframes_preview, or hyperframes_still, and no prerequisites mentioned. The agent must infer the context from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server