Skip to main content
Glama

transcribe

Convert local audio or video files into readable SRT and VTT captions with word-level timing, line-length limits, and standard or shorts styling; cached results make repeat requests free.

Instructions

Transcribe a local audio or video file into readable SRT and VTT captions (whole words, line-length and timing rules applied). style: 'standard' (2 lines x 42 chars) or 'shorts' (1-3 words, uppercase). Results are cached, so asking again for the same file is free.

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": "transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
styleNostandard
output_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses output formats, line-length/timing rules, style effects, and caching, but omits write side effects such as whether output_dir is created or overwritten, supported media formats, and error behavior.

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?

The description is front-loaded with the core action and output, then adds only relevant style and caching details. Every sentence earns its place and there is no unnecessary wording.

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?

For a three-parameter file-writing tool with no annotations and no output schema, the description covers purpose, output formats, style, and caching. However, it leaves output_dir semantics, return values, and file side effects unclear, so it is only adequately complete.

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. It explains the style values in useful detail and implies that path is a local media file, but output_dir is completely undocumented, leaving a significant parameter gap.

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 specific verb, 'Transcribe', and a specific resource, 'local audio or video file', plus the output formats SRT and VTT. It does not explicitly contrast with sibling voice/narration tools, so it falls short of full sibling differentiation.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and names no alternatives. It describes the style options but does not explain when an agent should choose 'standard' versus 'shorts'.

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