Skip to main content
Glama
misbahsy

Video & Audio Editing MCP Server

by misbahsy

set_video_resolution

Adjust video resolution to a specified target (e.g., '1920x1080') while preserving the audio stream. Input and output paths are required for processing.

Instructions

Sets the resolution 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 resolution. resolution: Target video resolution (e.g., '1920x1080', '1280x720', or '720' for height). Returns: A status message indicating success or failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_video_pathYes
output_video_pathYes
resolutionYes

Implementation Reference

  • The core handler function for the set_video_resolution MCP tool. It uses FFmpeg to scale the video to the target resolution via video filter (vf), attempts to copy the audio stream for efficiency, and falls back to full re-encoding if needed. Registered via @mcp.tool() decorator.
    @mcp.tool()
    def set_video_resolution(input_video_path: str, output_video_path: str, resolution: str) -> str:
        """Sets the resolution 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 resolution.
            resolution: Target video resolution (e.g., '1920x1080', '1280x720', or '720' for height).
        Returns:
            A status message indicating success or failure.
        """
        vf_filters = []
        if 'x' in resolution:
            vf_filters.append(f"scale={resolution}")
        else:
            vf_filters.append(f"scale=-2:{resolution}")
        vf_filter_str = ",".join(vf_filters)
        
        primary_kwargs = {'vf': vf_filter_str, 'acodec': 'copy'}
        fallback_kwargs = {'vf': vf_filter_str} # Re-encode audio
        return _run_ffmpeg_with_fallback(input_video_path, output_video_path, primary_kwargs, fallback_kwargs)
  • Supporting helper utility invoked by set_video_resolution (and similar tools) to execute FFmpeg operations with a primary attempt (e.g., stream copy) and fallback re-encoding on failure, providing consistent error handling and status messages.
    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, the description carries the full burden. It discloses that the tool attempts to copy the audio stream, which is a key behavioral trait, but lacks details on permissions, error handling, or side effects like file overwriting, which are important for a mutation tool.

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 sections for Args and Returns, and each sentence is purposeful. However, the 'attempting to copy the audio stream' clause could be integrated more smoothly, slightly affecting flow.

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 parameters well and hints at behavior, but lacks details on return values beyond a generic status message, leaving gaps in understanding outcomes.

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?

Schema description coverage is 0%, so the description must compensate. It fully explains all three parameters with clear examples (e.g., '1920x1080', '1280x720', or '720' for height) and specifies their roles, adding significant 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') and resource ('resolution of a video'), and distinguishes it from siblings by mentioning audio stream copying, which is unique among video processing tools like 'set_video_bitrate' or 'set_video_frame_rate'.

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 such as 'change_aspect_ratio' or 'set_video_codec', nor are there any prerequisites or exclusions mentioned, leaving the agent without context for 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