Skip to main content
Glama
mabh111111

FFmpeg Python MCP Server

by mabh111111
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

compress_video_with_qsv

Compresses video files using Intel Quick Sync Video (QSV) hardware acceleration, reducing file size while maintaining visual quality. Supports H.264 and H.265 encoding with adjustable quality and bitrate.

Instructions

使用Intel QSV硬件加速压缩视频

Args:
    input_path: 输入视频文件路径
    output_path: 输出视频文件路径（可选）
    quality: 压缩质量（high, medium, low）
    qsv_encoder: QSV编码器（h264_qsv, hevc_qsv等）
    target_bitrate: 目标比特率（如"2M", "1000k"）

Returns:
    压缩结果信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_pathYes
output_pathNo
qualityNomedium
qsv_encoderNoh264_qsv
target_bitrateNo

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations and description lacks behavioral traits like driver dependency, fallback behavior, or performance implications beyond mentioning hardware acceleration.

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?

Short docstring format, efficient with minimal prose, though parameter listing could be more streamlined.

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

Completeness2/5

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

Given 5 parameters, no output schema, and no annotations, the description omits return values, error handling, and prerequisites, leaving gaps.

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

Parameters2/5

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

Parameter list repeats schema info with no added constraints, examples, or formats; schema coverage is 0% and description does not compensate.

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?

Clearly states it compresses video using Intel QSV hardware acceleration, distinguishing from generic compress_video and convert_video_with_qsv siblings.

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?

No explicit guidance on when to use QSV vs software encoding or contrast with similar tools; usage is implied but not clarified.

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/mabh111111/ffmpeg_python_mcp'

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