Skip to main content
Glama

videogenie_media_probe

Runs ffprobe on an absolute local media path to inspect video files and return durable, bounded job results for project workflows.

Instructions

Run real ffprobe on an absolute local path with a durable bounded inline job.

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": {
      "project_id": "<project_id>",
      "storyline_id": "<storyline_id>",
      "path": "<path>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "videogenie_media_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
project_idYes
storyline_idYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successYes
project_idNo
request_idNo
storyline_idNo
schema_versionNo1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and mostly doesn't. 'Durable bounded inline job' hints at persistence and execution limits but never explains them: no timeout, file-access/permission requirements, failure behavior, or whether the result is returned synchronously. It also never states that idempotency_key controls duplicate suppression, which is the one behavioral detail an agent most needs for a mutation-ish invoke.

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 and the key constraint (absolute local path) placed early. The only cost is that the second half is compressed into unexpanded jargon rather than plain language.

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

Completeness3/5

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

An output schema exists, so return values needn't be described, and the core action is stated. But for a four-required-parameter tool with zero annotation coverage and zero schema documentation, the description does not supply enough for an agent to construct a valid call without guessing at three parameters and the job lifecycle.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all four required parameters, so the description must compensate and does so only for 'path' (absolute local path). It says nothing about project_id, storyline_id, or the 1-200 char idempotency_key, leaving three of four mandatory arguments semantically empty.

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?

States a concrete verb and resource: run ffprobe against an absolute local file path. An agent can tell this is a media-inspection tool, though the trailing phrase 'durable bounded inline job' is opaque jargon that doesn't clarify what the tool returns or how it relates to the job-related siblings.

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?

Implies usage via 'absolute local path', which tells the agent the precondition for the path argument, but gives no guidance on when to pick this over videogenie_job_get or videogenie_job_resume, nor when a probe should be re-run versus cached. No exclusions or alternatives are named.

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