Skip to main content
Glama
AbyAbyss

ffmpeg-mcp-video-editor

by AbyAbyss

Colour grade

color_grade

Correct or stylize video colors by adjusting brightness, contrast, saturation, gamma, and temperature in a single re-encode.

Instructions

Adjust brightness, contrast, saturation, gamma and colour temperature.

All five are applied in one filter chain, so the whole grade costs a single re-encode. Stages left at their neutral value are omitted entirely. Temperature is a relative artistic warm/cool control, not an absolute white balance in Kelvin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gammaNoMidtone curve; 1.0 leaves it alone.
encodeNo
contrastNoMultiplier; 1.0 leaves it alone.
brightnessNoAdditive lift; 0 leaves it alone.
input_pathYesPath to the source media file.
saturationNoMultiplier; 0 is greyscale, 1.0 unchanged.
output_pathNoDestination file. If omitted, the output is written into the job's workspace directory and its path is returned by job_result.
temperatureNoRelative warmth: negative is cooler and bluer, positive warmer and oranger.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes
job_idYes
statusNoqueued
messageNoJob queued. Poll job_status for progress, then job_result.
Behavior4/5

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

With annotations already signaling readOnly=false, the description adds useful behavioral context: neutral-value stages are omitted entirely and temperature is a relative artistic control, not an absolute white balance. This goes beyond what the schema and annotations alone provide.

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?

Three short sentences, each earning its place. Front-loads the action, then explains the filter chain efficiency and temperature semantics with zero fluff.

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

Completeness4/5

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

Given the output schema and high parameter coverage, the description covers purpose and key behavioral traits adequately. Missing is any comparison to sibling color tools, but the core workflow is understandable.

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 coverage is high, but the description adds meaningful clarification for temperature (relative warm/cool, not Kelvin) and the neutral-value omission rule. These insights help the agent understand the effects of leaving parameters at defaults.

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?

Description opens with 'Adjust brightness, contrast, saturation, gamma and colour temperature,' specifying the exact verb and resource. It clearly conveys what the tool does but does not contrast itself with sibling color tools like apply_curves or apply_lut.

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 description notes that all five adjustments are combined in one filter chain to require a single re-encode, implying it's efficient for multi-parameter grades. However, it doesn't explicitly state when to use this instead of apply_curves/apply_lut or when a grade is unnecessary.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AbyAbyss/ffmpeg-mcp-video-editor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server