Skip to main content
Glama
misbahsy

Video & Audio Editing MCP Server

by misbahsy

set_video_frame_rate

Change the frame rate of a video while preserving the audio stream. Specify input/output paths and target frame rate to adjust playback speed or compatibility.

Instructions

Sets the frame rate 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 frame rate. frame_rate: Target video frame rate (e.g., 24, 30, 60). Returns: A status message indicating success or failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frame_rateYes
input_video_pathYes
output_video_pathYes

Implementation Reference

  • The handler function that executes the set_video_frame_rate tool logic, using ffmpeg to set the video frame rate while attempting to copy the audio stream, with a fallback to re-encoding if necessary.
    @mcp.tool()
    def set_video_frame_rate(input_video_path: str, output_video_path: str, frame_rate: int) -> str:
        """Sets the frame rate 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 frame rate.
            frame_rate: Target video frame rate (e.g., 24, 30, 60).
        Returns:
            A status message indicating success or failure.
        """
        primary_kwargs = {'r': frame_rate, 'acodec': 'copy'}
        fallback_kwargs = {'r': frame_rate} # Re-encode audio
        return _run_ffmpeg_with_fallback(input_video_path, output_video_path, primary_kwargs, fallback_kwargs)
  • Supporting helper utility function used by the set_video_frame_rate handler (and other similar tools) to execute ffmpeg operations with a primary set of parameters and a fallback set.
    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)}"
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the tool modifies video frame rate, creates a new output file, and attempts to copy the audio stream (implying potential failure cases). However, it doesn't mention important details like whether the operation is destructive to the original file, what formats are supported, error conditions, or performance characteristics.

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 well-structured and efficiently organized: a clear purpose statement followed by dedicated 'Args' and 'Returns' sections. Every sentence earns its place by providing essential information without redundancy. The information is front-loaded with the core functionality stated first.

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 provides adequate basic information about what the tool does and its parameters. However, it lacks important context about behavioral details (error handling, supported formats, performance), and the return value description ('status message') is vague without specifying what success/failure messages look like.

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 has 0% description coverage, so the description must fully compensate. It provides clear semantic meaning for all three parameters: 'input_video_path' as source file path, 'output_video_path' as destination for the modified video, and 'frame_rate' as target frame rate with examples (24, 30, 60). This adds substantial value beyond the bare 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 the tool's purpose with a specific verb ('Sets'), resource ('frame rate of a video'), and scope ('attempting to copy the audio stream'). It distinguishes itself from sibling tools like 'change_video_speed' or 'set_video_bitrate' by focusing specifically on frame rate adjustment with audio preservation.

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 context through the parameter descriptions and the mention of audio stream copying, suggesting it's for frame rate conversion while preserving audio. However, it doesn't explicitly state when to use this versus alternatives like 'change_video_speed' (which might affect audio pitch) or other video processing tools, nor does it mention any prerequisites or exclusions.

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