Skip to main content
Glama

TranscriptLab

Discover caption tracks

transcriptlab_discover_captions
Read-only

List the caption languages and track types (manual vs generated) available for a YouTube video. Use when the user asks which languages or subtitles a video has, or before transcriptlab_get_transcript when they want a specific language. Free in transcript credits, but subject to the account monthly discovery limit.

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_discover_captions"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video URL or 11-character video ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond them by disclosing quota behavior — free in transcript credits but subject to the account's monthly discovery limit — which is exactly the kind of constraint an agent needs before calling. It does not describe output shape, though it does state what categories of information come back, so it falls just short of full transparency.

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 tight sentences: capability first, then usage triggers, then cost constraint. Nothing is redundant with the title, and the quota caveat is placed last where it belongs.

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 single-parameter read-only discovery tool with full annotation coverage and no output schema, the description supplies purpose, triggers, sibling relationship, and quota cost. Everything an agent needs to decide and call correctly is present.

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?

With one parameter at 100% schema coverage, the schema already documents the URL-or-11-character-ID format. The description reinforces that the target must be a YouTube video, resolving any ambiguity about accepted sources and tying the parameter back to the tool's scope.

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 — list caption languages and track types (manual vs generated) — for a YouTube video. It also names the sibling transcriptlab_get_transcript as the downstream consumer, so an agent can distinguish it from transcript-fetching tools without reading any 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?

Explicitly gives both trigger conditions: when the user asks which languages or subtitles exist, and as a precursor to transcriptlab_get_transcript when a specific language is wanted. That covers when-to-use and the sequencing/alternative relationship in one clause.

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.