Skip to main content
Glama

TranscriptLab

Transcribe an attached audio or video file

transcriptlab_transcribe_file

Transcribe an audio or video file the user attached to this conversation, using speech-to-text (mp3, m4a, wav, mp4, webm and similar). Use it for an attached media file; YouTube links use transcriptlab_get_transcript instead. Spends credits per audio minute. Attachments up to 300 MB work here; larger files (up to 2 GB) use the launcher upload view. Stores the file, starts transcription, and returns an upload_id: poll transcriptlab_get_speech_transcript with it, waiting a few seconds between tries and stopping after about ten. Do not call this again for the same file. If it fails or the file is too large, call transcriptlab_open with tab "upload".

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": {
      "file": "<file>"
    },
    "name": "transcriptlab_transcribe_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesThe attached media file.
tierNoSpeech model tier; defaults to auto (normal when available).
diarizeNoLabel speakers; defaults to false. Implies tier=premium.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations only declare non-read-only, open-world, non-destructive; the description adds credit consumption per audio minute, the 300 MB attachment cutoff vs 2 GB via launcher upload, that the file is stored server-side and transcription started, the returned upload_id, and a polling cadence (~a few seconds, stop after ~ten tries). These are operational facts the annotations cannot convey.

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-loaded with what it does and the sibling routing, then cost, size limit, return value, polling, and fallback in tight imperative sentences. No sentence is filler despite the density.

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

Completeness5/5

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

For a write-like tool with no output schema, the description still supplies the return contract (upload_id), the follow-up call to poll, retry bounds, size limits, and an error path. Nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3; the description nonetheless adds the practical constraint that larger files must go through the upload launcher rather than this call, which shapes how the file argument can be used.

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 concrete verb and resource (transcribe an attached audio/video file) and names supported formats plus the alternate route for YouTube links via transcriptlab_get_transcript. An agent can distinguish this from transcriptlab_transcribe_media_url and the link-based siblings without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (attached media file), when-not (YouTube links go to transcriptlab_get_transcript), a no-retry rule ('Do not call this again for the same file'), and a failure fallback (transcriptlab_open with tab "upload"). Alternatives are named with the condition that selects each.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.