Skip to main content
Glama
misbahsy

Video & Audio Editing MCP Server

by misbahsy

set_video_bitrate

Adjust video bitrate for optimal file size and quality. Specify input and output paths along with the desired bitrate to process and save videos effectively.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_video_pathYes
output_video_pathYes
video_bitrateYes

Implementation Reference

  • The main handler function for the 'set_video_bitrate' MCP tool, decorated with @mcp.tool(). It sets the video bitrate using FFmpeg, attempting to copy the audio stream first and falling back to full re-encoding if needed.
    @mcp.tool()
    def set_video_bitrate(input_video_path: str, output_video_path: str, video_bitrate: str) -> str:
        """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.
        """
        primary_kwargs = {'video_bitrate': video_bitrate, 'acodec': 'copy'}
        fallback_kwargs = {'video_bitrate': video_bitrate} # Re-encode audio
        return _run_ffmpeg_with_fallback(input_video_path, output_video_path, primary_kwargs, fallback_kwargs)
  • Helper function _run_ffmpeg_with_fallback called by set_video_bitrate (and other tools) to execute FFmpeg with primary parameters (e.g., audio copy) and fallback to re-encoding on error.
    def _run_ffmpeg_with_fallback(input_path: str, output_path: str, primary_kwargs: dict, fallback_kwargs: dict) -> str:
        """Helper to run ffmpeg command with primary kwargs, falling back to other kwargs on ffmpeg.Error."""
        try:
            ffmpeg.input(input_path).output(output_path, **primary_kwargs).run(capture_stdout=True, capture_stderr=True)
            return f"Operation successful (primary method) and saved to {output_path}"
        except ffmpeg.Error as e_primary:
            try:
                ffmpeg.input(input_path).output(output_path, **fallback_kwargs).run(capture_stdout=True, capture_stderr=True)
                return f"Operation successful (fallback method) and saved to {output_path}"
            except ffmpeg.Error as e_fallback:
                err_primary_msg = e_primary.stderr.decode('utf8') if e_primary.stderr else str(e_primary)
                err_fallback_msg = e_fallback.stderr.decode('utf8') if e_fallback.stderr else str(e_fallback)
                return f"Error. Primary method failed: {err_primary_msg}. Fallback method also failed: {err_fallback_msg}"
        except FileNotFoundError:
            return f"Error: Input file not found at {input_path}"
        except Exception as e:
            return f"An unexpected error occurred: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation and return format. It lacks details on permissions, side effects, error handling, or performance characteristics (e.g., processing time, file size changes). The phrase 'attempting to copy' hints at potential failure but doesn't elaborate.

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 well-structured with purpose statement, Args section, and Returns section. It's appropriately sized with no redundant information, though the 'attempting to copy' phrase could be more precise. Every sentence serves a clear purpose.

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?

For a mutation tool with no annotations and no output schema, the description covers the basic operation and parameters adequately but lacks depth on behavioral aspects like error conditions, audio handling guarantees, or output specifics. It's minimally viable but leaves gaps for safe agent invocation.

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 description coverage is 0%, so the description must compensate. It provides clear explanations for all three parameters, including examples for video_bitrate ('e.g., '1M', '2500k''), which adds meaningful context beyond the bare schema. However, it doesn't specify path formats or constraints.

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 the specific action ('Sets the video bitrate of a video') and resource ('a video'), with the additional detail 'attempting to copy the audio stream' that distinguishes it from sibling tools like set_video_audio_track_bitrate. It precisely communicates what the tool does beyond just the name.

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 implies usage for video bitrate adjustment with audio preservation, but does not explicitly state when to use this tool versus alternatives like set_video_audio_track_bitrate or convert_video_properties. No exclusions or prerequisites are mentioned, leaving some ambiguity in tool selection.

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

Related 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/misbahsy/video-audio-mcp'

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