Skip to main content
Glama

TranscriptLab

Transcribe a direct media link

transcriptlab_transcribe_media_url

Transcribe a public https link to an audio or video file with speech-to-text. Use it for a direct media URL (ending in .mp3, .m4a, .wav, .mp4, .webm and similar); not for YouTube or other web pages, which use transcriptlab_get_transcript. Spends credits per audio minute. Returns a media_id: poll transcriptlab_get_speech_transcript with it, waiting a few seconds between tries and stopping after about ten.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https URL of an audio or video 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

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description goes well beyond them by disclosing the cost model (credits per audio minute) and the asynchronous contract (returns a media_id rather than the transcript, poll separately with a retry cadence and stop condition). Those are the two facts an agent most needs before calling a paid, non-immediate operation.

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?

Three dense sentences with no filler: what it does and the input shape first, the exclusion and alternative second, cost and the follow-up flow last. Every sentence carries information an agent needs at call time.

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?

There is no output schema, and the description compensates by explaining exactly what comes back (a media_id) and how to redeem it. Combined with the credit cost and the tier/diarize defaults already in the schema, nothing material is missing for a correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents url, tier and diarize, establishing a baseline of 3. The description still adds meaning the schema lacks: the URL must be a direct media file with a recognizable extension rather than a web page, which is the main way the required parameter can be passed incorrectly.

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 specific verb and resource ("Transcribe a public https link to an audio or video file with speech-to-text") and immediately scopes the input type with concrete extensions (.mp3, .m4a, .wav, .mp4, .webm). It explicitly separates itself from transcriptlab_get_transcript for YouTube/web pages, so an agent can route correctly 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 Guidelines5/5

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

Gives both sides of the decision: use for a direct media URL, not for YouTube or other web pages, naming the alternative tool to use instead. It also prescribes the downstream sequence — poll transcriptlab_get_speech_transcript with the returned media_id, a few seconds apart, stopping after about ten tries.

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.