Skip to main content
Glama

TranscriptLab

Create a download link

transcriptlab_export_link
Read-only

Create a 10-minute signed download link (TXT, SRT, VTT, Markdown, or JSON) for a transcript the account already has, or for a transcribed upload. Call this when the user wants a file or a link to a file: hand them the returned url and say it expires in 10 minutes. Needs a signed-in connection. The launcher Download action calls it too, so a host that cannot start a download itself still gives the user the link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "transcriptlab_export_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoYouTube video URL or 11-character video ID.
langNo
formatNo
upload_idNoUpload id of a transcribed file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), but the description adds what they don't: the link is signed, expires in 10 minutes, requires a signed-in connection, and the agent should tell the user about expiry. It doesn't discuss rate limits or whether repeated calls produce different links.

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?

Four sentences with the core action, format list and expiry front-loaded. The final sentence about the launcher Download action is useful but slightly tangential; overall there is little padding.

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?

With no output schema, the description usefully says to hand the user the returned url and note the expiry, covering the return value. The auth requirement is stated. The remaining gap is the url-vs-upload_id selection rule for a 4-param tool with no required fields.

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 coverage is 50%: url and upload_id are documented in the schema, lang and format are not, though the format enum is self-explanatory and the description spells out the five formats. With 0 required parameters, the critical missing semantics is whether url and upload_id are mutually exclusive sources, which the description never clarifies.

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 ('Create a 10-minute signed download link') plus the source ('a transcript the account already has, or a transcribed upload') and the output formats. This clearly separates it from sibling tools that return transcript content directly rather than a file link.

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?

Gives a clear trigger condition: 'Call this when the user wants a file or a link to a file.' It also mentions the launcher Download action as a second caller. It lacks explicit when-not guidance or named alternatives among siblings, but the trigger is unambiguous.

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.