mcp-ffmpeg

Overview Schema Source Related Servers Discussions Admin

set_video_bitrate

Set a video bitrate to control file size and quality, copying the audio stream unchanged. Provide input path, output path, and target bitrate (e.g., '1M').

Instructions

Sets the video bitrate of a video, attempting to copy the audio stream.

Args: input_video_path: Path to the source video file. output_video_path: Path to save the video with the new video bitrate. video_bitrate: Target video bitrate (e.g., '1M', '2500k'). Returns: A status message indicating success or failure.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input_video_path": "<input_video_path>",
      "output_video_path": "<output_video_path>",
      "video_bitrate": "<video_bitrate>"
    },
    "name": "set_video_bitrate"
  }
}

Input Schema

Name	Required	Description	Default
`video_bitrate`	Yes
`input_video_path`	Yes
`output_video_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The description includes a behavioral note: 'attempting to copy the audio stream', which implies the video will be re-encoded and audio preserved. However, it does not disclose potential downsides like quality loss, file size changes, or any failure conditions. With no annotations to rely on, the description only partially carries the transparency burden.

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 concise and well-structured: a one-sentence summary, followed by a bulleted Args list, and a Returns line. Each sentence earns its place with no redundancy or 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 3-param tool with no annotations, the description covers the key aspects: all parameters are explained, the return value is indicated, and the crucial audio-copy behavior is mentioned. Minor gaps include no mention of error handling or supported formats, but the essential information for correct invocation is present.

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

Parameters5/5

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

The schema provides no descriptions (0% coverage), but the description's Args section fully explains each parameter: input_video_path is the source, output_video_path is the destination, and video_bitrate includes format examples ('1M', '2500k'). This adds significant meaning beyond the raw schema, which only lists names.

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 states a specific verb+resource: 'Sets the video bitrate of a video'. It distinguishes itself from audio bitrate tools by explicitly mentioning video, and adds a nuance about attempting to copy the audio stream. This clearly identifies its purpose among sibling 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 guidance is given on when to use this tool versus alternatives. It doesn't mention exclusions, related tools, or scenarios where another tool would be more appropriate. The description is purely functional without contextual usage advice.

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