Skip to main content
Glama

transcribe_video

Generate local speech transcripts for captionless videos using Whisper; specify start and end times to process long videos in 30-minute segments.

Instructions

Transcribe the SPEECH of a video locally with Whisper (faster-whisper, CPU) when it has no usable captions. model: tiny | base | small (bigger = slower, more accurate). lang: 'en', 'tr'... or empty to auto-detect. Max 30 min per call, so use start/end for long videos. First run downloads the model once.

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": {
      "url": "<url>"
    },
    "name": "transcribe_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
urlYes
langNo
modelNobase
startNo
max_charsNo
chunk_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses local/CPU execution, the per-call 30-minute cap, the accuracy-vs-speed tradeoff of the model tiers, and the one-time first-run model download (a real latency cost agents should anticipate). It stops short of covering failure modes or how partial results are returned, so not a 5.

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?

Front-loads purpose, then appends only the parameter and constraint notes an agent actually needs, in a compact telegraphic style with no filler. Every clause carries operational information.

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 7-parameter tool with zero schema coverage, the description supplies the decisive facts: when to call it, model selection tradeoff, language handling, the 30-minute limit, and first-run download cost. The presence of an output schema removes the need to describe return values, though the unexplained max_chars/chunk_seconds leave a small gap.

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 0%, so the description must compensate, and it explains model tiers, lang values/auto-detect, and start/end usage in ways the schema does not. However, url, max_chars, and chunk_seconds (the majority of the 7 parameters) get no mention anywhere, so roughly half the surface remains undocumented.

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?

Names a specific verb plus resource ('Transcribe the SPEECH of a video'), adds the mechanism (Whisper/faster-whisper, local, CPU), and qualifies the condition ('when it has no usable captions') that separates it from the caption-fetching transcripts sibling. An agent can route between this and video_transcript without opening either schema.

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?

Explicit when-to-use condition ('when it has no usable captions') plus practical direction for long inputs ('use start/end for long videos'). It never names a concrete alternative tool nor states when NOT to use it, which keeps it below a 5.

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