Skip to main content
Glama

Convert video format

video_convert
Destructive

Convert video files to different container or codec formats like mp4, webm, gif, or mov. Adjust encoding quality with presets from low to ultra.

Instructions

Transcode an existing video into a different container or codec format such as mp4, webm, gif, or mov. Use this for format conversion; use video_export for final delivery presets. The input video is read only and a new output file is rendered.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_pathYesAbsolute path to an existing local video file. The input file is read only.
formatNoTarget output format. Supported values are mp4, webm, gif, and mov.mp4
qualityNoEncoding quality preset: low, medium, high, or ultra.high
output_pathNoDestination video path. Auto-generated when omitted; an existing supplied path may be overwritten.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses that the input video is read only and a new output file is rendered, with potential overwrite. This adds context beyond annotations, though no additional info on permissions or rate limits.

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?

Two sentences, no redundant information, and the main purpose is front-loaded.

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

Completeness4/5

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

Covers purpose, behavior, and sibling distinction. Output schema exists but details not needed for usage. Could mention error handling, but sufficient for a conversion tool.

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 coverage is 100%, so baseline is 3. The description does not add extra meaning beyond the schema descriptions for parameters.

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 it transcodes an existing video into formats like mp4, webm, gif, or mov. It distinguishes from the sibling tool video_export by specifying format conversion vs final delivery presets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says 'Use this for format conversion; use video_export for final delivery presets.' This directly tells the agent when to use this tool versus an alternative.

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

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/KyaniteLabs/mcp-video'

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