Skip to main content
Glama
misbahsy

Video & Audio Editing MCP Server

by misbahsy

set_video_audio_track_sample_rate

Adjust the audio sample rate of a video's audio track while preserving the video stream. Specify input and output video paths along with the desired sample rate in Hz.

Instructions

Sets the audio sample rate of a video's audio track, attempting to copy the video stream. Args: input_video_path: Path to the source video file. output_video_path: Path to save the video with the new audio sample rate. audio_sample_rate: Target audio sample rate in Hz (e.g., 44100, 48000). Returns: A status message indicating success or failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_sample_rateYes
input_video_pathYes
output_video_pathYes

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the tool logic using FFmpeg to set the video's audio track sample rate, preferring to copy the video stream and falling back to re-encoding if necessary.
    @mcp.tool()
    def set_video_audio_track_sample_rate(input_video_path: str, output_video_path: str, audio_sample_rate: int) -> str:
        """Sets the audio sample rate of a video's audio track, attempting to copy the video stream.
        Args:
            input_video_path: Path to the source video file.
            output_video_path: Path to save the video with the new audio sample rate.
            audio_sample_rate: Target audio sample rate in Hz (e.g., 44100, 48000).
        Returns:
            A status message indicating success or failure.
        """
        primary_kwargs = {'ar': audio_sample_rate, 'vcodec': 'copy'} # ar for audio sample rate
        fallback_kwargs = {'ar': audio_sample_rate} # Re-encode video
        return _run_ffmpeg_with_fallback(input_video_path, output_video_path, primary_kwargs, fallback_kwargs)
  • Supporting helper function used by the tool handler to execute FFmpeg commands with a fallback from stream-copy to re-encoding.
    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 for behavioral disclosure. It mentions 'attempting to copy the video stream' which hints at partial failure modes, but doesn't cover permissions needed, file format limitations, whether original files are modified, error handling, or performance characteristics. For a mutation tool with zero annotation coverage, this is insufficient.

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?

Well-structured with purpose statement followed by Args and Returns sections. The description is appropriately sized with no redundant information. Every sentence serves a clear purpose, though the 'attempting to copy' clause could be more precisely worded.

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 parameters and purpose but lacks important behavioral context. It doesn't explain what 'success or failure' means in practice, nor does it address file system implications or compatibility constraints that would help an agent use it correctly.

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 meaning for all three parameters: 'input_video_path' as source file path, 'output_video_path' as destination path, and 'audio_sample_rate' as target rate in Hz with examples (44100, 48000). 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 specific action ('Sets the audio sample rate of a video's audio track') and resource ('video's audio track'), with the additional detail 'attempting to copy the video stream' that distinguishes it from other audio/video processing tools. 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'set_audio_sample_rate' or other audio/video processing siblings. The description lacks context about prerequisites, typical use cases, or comparisons to similar tools in the server.

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