Skip to main content
Glama
kevinwatt

FFmpeg MCP

by kevinwatt
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

ffmpeg_convert

Convert video and audio files to different formats. Specify output format, and optionally set resolution, video codec, and audio codec for precise control.

Instructions

Convert video/audio to a different format.

Args:
    file_path: Path to the input media file
    output_format: Target format (e.g., mp4, mkv, webm, mp3, wav)
    scale: Optional resolution scale (e.g., "1280:720", "1920:-1" for auto height)
    video_codec: Optional video codec (e.g., libx264, libx265, libvpx-vp9)
    audio_codec: Optional audio codec (e.g., aac, mp3, opus)

Returns:
    Path to the converted file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
output_formatYes
scaleNo
video_codecNo
audio_codecNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description should disclose behavioral traits, but it only states the return type and does not mention error handling, overwrite behavior, or other side effects.

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?

The description is a well-structured docstring with clearly labeled Args and Returns sections, and contains no unnecessary words.

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?

Given the tool's moderate complexity (5 parameters, some optional) and the presence of an output schema, the description covers the essential aspects but lacks details on edge cases and usage context.

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?

With 0% schema description coverage, the description compensates by providing examples for scale and codec parameters, and explaining output_format. However, it could be more precise about allowed values.

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 'Convert video/audio to a different format' with a specific verb and resource, and it is distinct from sibling tools like ffmpeg_extract_audio, ffmpeg_compress, etc.

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?

The description does not provide any guidance on when to use this tool versus the siblings, nor does it mention when not to use it or alternative tools.

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/kevinwatt/ffmpeg-mcp-lite'

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