Skip to main content
Glama

Get Media Info

get_media_info
Read-onlyIdempotent

Probe a media file to retrieve duration, resolution, frame rate, codecs, container format, and file size before editing or inspecting recordings.

Instructions

Probe a media file with ffprobe and return duration, resolution, frame rate, codecs, container format, and size.

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

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the media file to probe.

Output Schema

NameRequiredDescriptionDefault
fpsYes
inputYes
widthYes
heightYes
audioCodecYes
videoCodecYes
durationSecYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.47.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "audioCodec": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "durationSec": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "fps": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "height": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "input": {
      +      "type": "string"
      +    },
      +    "videoCodec": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "width": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "input",
      +    "durationSec",
      +    "width",
      +    "height",
      +    "fps",
      +    "videoCodec",
      +    "audioCodec"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds the mechanism (ffprobe) which hints at behavior on unsupported files, but does not say what happens on a missing/corrupt file or whether probing is slow for large media.

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?

One sentence, front-loaded with the verb and resource, then the return payload. No filler, nothing repeated from structured fields.

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 present and annotations fully populated, the description only needs to establish what the tool does and on what input, which it does. It stops short of covering failure modes or path requirements for a tool whose whole risk surface is 'file may not exist.'

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% with a single, well-documented 'input' path parameter, so the schema carries the load. The description adds nothing about accepted path forms (local vs remote, relative vs absolute) or whether the path must already exist.

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 (probe), a specific resource (a media file), the mechanism used (ffprobe), and enumerates the exact fields returned. An agent can distinguish it from siblings like get_session or read_events purely from the text.

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 agent can infer this is a pre-flight inspection step before convert/compress/trim, but the description never says when to call it versus alternatives or whether it is a prerequisite for other tools. No exclusions or prerequisites are stated.

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