Skip to main content
Glama
Sign In
FFmpeg MCP Server

FFmpeg MCP Server

by ZizoTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

speed_up

Increase video playback speed with configurable FPS and speed factor using FFmpeg MCP Server. Specify input/output files and adjust parameters for precise control.

Instructions

Speed up a video

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_file": "<input_file>"
    },
    "name": "speed_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_fileYesPath to input file
max_fpsNoMax FPS for the output file
output_fileNoPath to output file, output to the same directory if not specified
speed_factorNoSpeed factor for the output file, default to 2x sped up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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. While 'speed up' implies a transformation operation, it doesn't disclose whether this is destructive to the original file, what permissions are needed, or any rate limits. The description lacks essential behavioral context 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just three words, front-loading the core purpose without any wasted language. Every word earns its place in this minimal but clear statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a video processing tool with 4 parameters and no annotations or output schema, the description is insufficient. It doesn't explain what the tool returns, what happens to the original file, or provide any context about the processing operation beyond the basic purpose.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already fully documents all four parameters. The description adds no additional parameter information beyond what's in the schema, meeting the baseline expectation but not providing extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('speed up') and resource ('a video'), making the purpose immediately understandable. However, it doesn't differentiate from the sibling tool 'extract_audio', which handles a different video processing function.

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 about when to use this tool versus alternatives. The description doesn't mention the sibling tool 'extract_audio' or any other video processing options, 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.

Deploy Server

Other Tools

Related Tools