ffmpeg-render-pro

Overview Schema Source Related Servers Discussions Admin

Color Grade Video

color_grade

Destructive

Apply a color grade to a video file using presets (noir, warm, cool, cinematic, vintage) or a custom ffmpeg filter, writing the result to a new output file.

Instructions

Apply a color grade to a video file and write the result to a new file. Provide either a built-in preset (noir, warm, cool, cinematic, vintage) or a custom ffmpeg -vf filter string (filter overrides preset). Re-encodes the video stream with the chosen codec; audio is stripped unless keep_audio is true. Prerequisite: ffmpeg installed. Side effect: overwrites output_path if it already exists.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`crf`	No	CRF/CQ quality, 0-51. Lower is higher quality. Default 18.
`codec`	No	Video encoder for the output. Default libx264.	libx264
`filter`	No	Custom ffmpeg -vf filter string. Overrides preset when both are given.
`preset`	No	Built-in color grade preset
`input_path`	Yes	Input video file path. Must exist.
`keep_audio`	No	Stream-copy the input audio track instead of stripping it. Default false (audio stripped).
`output_path`	Yes	Output video file path. Overwritten if it already exists.

Output Schema

TableJSON Schema

Name	Required	Description
`crf`	Yes	CRF/CQ quality value applied
`codec`	Yes	Encoder used for the output
`filter`	Yes	Custom filter applied, or null when a preset was used
`preset`	Yes	Preset applied, or null when a custom filter was used
`audioKept`	Yes	True when the input audio track was stream-copied into the output
`inputPath`	Yes	Absolute input file path
`outputPath`	Yes	Absolute output file path

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.2Sep 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description openly discloses the destructive side effect of overwriting output_path, re-encoding behavior, and the default stripping of audio, all consistent with the destructiveHint annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single well-organized paragraph covering purpose, modes, processing behavior, prerequisite, and side effect without unnecessary verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It includes the required prerequisite (ffmpeg installed) and the key side effect (overwrite), making the tool's behavior fully understandable even without inspecting the output schema.

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?

The schema already documents all seven parameters with descriptions, and the description adds context about re-encoding and the relationship between preset and filter beyond the schema fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool applies a color grade to a video file and writes the result to a new file, which is specific and distinguishes it from rendering, merging, or concatenating videos.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains how to choose between a preset and a custom filter, and clarifies the audio handling behavior. It does not explicitly contrast with sibling tools, but the intent is unambiguous.

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

Deploy Server