Skip to main content
Glama
Sign In
mcp-ffmpeg

mcp-ffmpeg

by pauloFroes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get Media Info

get_media_info
Read-only

Retrieve metadata from local media files: duration, resolution, codecs, format, and file size. Uses ffprobe for accurate analysis.

Instructions

Get metadata about a local media file (video or audio): duration, resolution, codecs, format, filesize. Uses ffprobe.

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": {
      "file_path": "<file_path>"
    },
    "name": "get_media_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path to a local media file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds value by specifying 'Uses ffprobe' (external tool) and 'local media file' constraint. No contradictions; the description complements annotations well.

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 with no superfluous content. Every word adds value: verb, resource, specific metadata fields, tool used. Front-loaded with key purpose.

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

Completeness5/5

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

Given no output schema, the description compensates by listing returned fields (duration, resolution, etc.) and the underlying method (ffprobe). Sufficient for a simple read-only 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%, and the description only repeats 'local media file' which is already in the schema parameter description. No additional semantic value beyond reinforcing the context.

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 'Get metadata about a local media file (video or audio)' with specific fields listed (duration, resolution, etc.), using a specific verb and resource. It distinguishes from sibling tools like extract_audio which have different purposes.

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?

The description implies usage when metadata is needed but does not explicitly state when to use this tool versus alternatives, nor provide any when-not-to-use guidance. No mention of prerequisite checks or context.

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