Skip to main content
Glama
Sign In
video-brief-mcp

video-brief-mcp

by Artem-Pavlenko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Inspect a video

brief_probe
Read-only

Probe a video or audio file for duration, resolution, fps, audio track, size, and transcript-cache status before transcribing or extracting frames.

Instructions

Duration, resolution, fps, audio track, size, and whether a transcript is already cached. Start here.

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": {
      "path": "<path>"
    },
    "name": "brief_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the video (or audio) file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false), and the description usefully discloses the returned field set, including the notable 'whether a transcript is already cached' signal that lets an agent skip work. Beyond that it says nothing about error behavior, unsupported formats, or cost, so with annotations doing the safety work a 3 is fair.

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 short sentences, front-loaded with the output inventory and closed with the routing instruction. Nothing is padded and nothing needs to be reread.

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?

For a one-parameter read-only probe with no output schema, the description covers the essential unknowns by listing the returned fields, so an agent knows what it gets before calling. Minor omissions — supported container formats and failure behavior for unreadable paths — keep it from a 5.

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% with a single required parameter, and the schema already states 'Absolute path to the video (or audio) file'. The mention of 'audio track' implicitly confirms audio-only inputs are supported, which is marginal added meaning; baseline 3 applies when the schema carries the load.

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 enumerates exactly what the tool surfaces — duration, resolution, fps, audio track, size, and cached-transcript status — so an agent can tell this is a metadata probe distinct from brief_transcribe or brief_frames. It lacks an explicit verb, relying on the title 'Inspect a video' and the field list to convey the action.

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

Usage Guidelines4/5

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

'Start here' explicitly positions this as the entry point of the workflow, which is a real and useful routing cue against the five sibling tools. It stops short of naming alternatives or stating when not to use it, so it does not reach the top of the scale.

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