Skip to main content
Glama

Convert Format

convert
Destructive

Convert source media into mp4 (H.264), webm (VP9), or gif files, with optional fps, width, and output path settings. Use it when a recording or clip must be re-encoded to a different format.

Instructions

Convert media to mp4, webm, or gif. For a size-bounded GIF/WebP prefer export_gif; for a smaller mp4, compress or export_preset.

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": "<input>",
      "format": "<format>"
    },
    "name": "convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNogif only: fps (default 12).
inputYesPath to the source media.
widthNogif only: width in px (default 720).
formatYesmp4 (H.264), webm (VP9), or gif (palette).
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
overwriteNoAllow replacing an existing file at the output path (default false).

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.47.0
    • changedInput schema / properties / format / description
      Previous value: -"Target format. Converts mp4 <-> gif/webm (H.264 / VP9 / palette gif)."New value: +"mp4 (H.264), webm (VP9), or gif (palette)."
    • changedInput schema / properties / fps / description
      Previous value: -"Output fps (gif only; default 12)."New value: +"gif only: fps (default 12)."
    • changedInput schema / properties / width / description
      Previous value: -"Output width in px, height auto (gif only; default 720)."New value: +"gif only: width in px (default 720)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "outputPath": {
      +      "description": "Path of the file written.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "outputPath"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, non-idempotent, and non-read-only behavior, so the safety profile is covered. The description adds format-specific intent but does not elaborate on overwrite behavior, side effects, or output handling beyond what the schema already states.

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 compact sentences with the core action front-loaded and alternatives immediately afterward. There is no wasted prose.

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?

With an output schema and fully described input schema, the description does not need to explain return values or parameter syntax. It is nearly complete, though it could clarify overwrite/destructive behavior slightly more given that the tool writes files.

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 all six parameters including fps, width, format, output, and overwrite are documented in the schema. The description adds no parameter-level detail beyond the format list, which is already covered by the schema's format enum.

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?

States a specific verb and resource (convert media) and enumerates the exact output formats, so the agent can distinguish it from generic editing tools. It also names sibling alternatives for specific cases, making the tool's scope clear.

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 routes the agent away from this tool when a size-bounded GIF/WebP is desired (prefer export_gif) and when a smaller mp4 is desired (compress or export_preset). That is concrete alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.