Skip to main content
Glama

video_filter

Apply visual filters to videos including blur, color presets, and adjustments like brightness, grayscale, or vignette. Supports various filter parameters and encoding options.

Instructions

Apply a visual filter to a video.

Common presets: - blur: params={"radius": 5, "strength": 1} - color_preset: params={"preset": "warm"} (warm, cool, vintage, cinematic, noir)

Args: input_path: Absolute path to the input video. filter_type: Filter type (blur, sharpen, brightness, contrast, saturation," " grayscale, sepia, invert, vignette, color_preset, denoise," " deinterlace, ken_burns, reverb, compressor, pitch_shift," " noise_reduction). params: Optional filter parameters (e.g. radius for blur, preset for color_preset). output_path: Where to save the output. Auto-generated if omitted. crf: Override CRF value (0-51, lower = better quality). Default 23. preset: Override FFmpeg encoding preset (ultrafast, fast, medium, slow, veryslow).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_pathYes
filter_typeYes
paramsNo
output_pathNo
crfNo
presetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so description carries full burden. It reveals that output_path auto-generates if omitted, but lacks details on destructiveness, permission requirements, or side effects like file modification. Insufficient for a mutation tool.

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?

Description is reasonably sized with clear sections (common presets, Args list). Minor redundancy and incomplete filter_type list, but overall efficient and front-loaded with key examples.

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?

Covers basic usage and parameter roles, but lacks details on return values, filter combination, or processing order. Output schema exists, reducing need for return info, but context about limitations or chaining is missing. Adequate but not thorough.

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?

With 0% schema description coverage, description adds meaning by explaining parameters like input_path, filter_type, params (with examples), crf, and preset. However, filter_type list is incomplete, and param details are limited. Provides moderate value beyond schema.

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 it applies a visual filter to a video, with a specific verb ('apply') and resource ('visual filter'). Examples of common presets further clarify functionality, distinguishing it from sibling audio-specific or single-effect tools.

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?

No explicit guidance on when to use this tool versus alternatives like specific effect tools or audio filtering tools. The description does not mention when not to use it or provide context for choosing this tool over siblings.

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/KyaniteLabs/mcp-video'

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