Skip to main content
Glama
ffmpeg-mcp

ffmpeg-mcp

by yambal

get_media_info

Retrieves detailed metadata and technical information about an audio or video file from a specified input path before processing or conversion.

Instructions

Get detailed information about an audio or video file

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_path": "<input_path>"
    },
    "name": "get_media_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_pathYesPath to the input media file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Get' weakly implies a read-only, non-destructive operation, but the definition never states what information is returned (duration, codec, bitrate, resolution, streams), whether the file is opened or probed, or what happens for unsupported or corrupt files — all material for a tool with no annotation coverage.

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?

A single front-loaded sentence with no filler, correctly emphasizing the resource and the read intent. It is compact but borders on under-specification rather than wasteful verbosity.

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?

With no annotations and no output schema, the description must explain what 'detailed information' comprises, and it does not — an agent cannot tell whether it will receive duration, codec, dimensions, or stream listings. For an otherwise simple one-parameter tool this leaves the most important unknown (the return content) unresolved.

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% and there is only one parameter, so the baseline is 3. The description does add one piece of meaning by clarifying the input may be either audio or video, whereas the schema only says 'media file', but it adds nothing about path format, relative vs absolute, or handling of remote paths.

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 states a specific verb and resource ('Get detailed information about an audio or video file'), which an agent can distinguish from the sibling tools that all mutate or transform media. It stops short of explicitly naming a sibling or stating it is the only read/inspection tool, so differentiation is inferential rather than explicit.

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

Usage Guidelines3/5

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

Usage is only implied: the 'detailed information' framing suggests inspection rather than processing, which fits naturally before convert_audio or trim_audio. There is no explicit when-to-use condition, no exclusions, and no alternative named, leaving the agent to infer placement in a workflow.

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