Skip to main content
Glama

transcript_get

Returns the full transcript of the playing video or subtitle file as timed cues with speaker labels, enabling reading, summarising, or chapter-list creation.

Instructions

Return the full transcript of the currently playing file as timed cues (including speaker labels when present), plus where it came from. Use it to read or summarise a video, or as input for writing your own chapter list with set_chapters. Long videos produce a lot of text — prefer search_transcript or transcript_summary when you only need a passage or overview.

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

Input Schema

NameRequiredDescriptionDefault
fileNoOptional path to a video or subtitle file; defaults to the playing file
speakerNoOptional speaker filter (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose return shape (timed cues, speaker labels when present, source of the transcript) and a real behavioral trait: long videos produce a lot of text. It does not discuss error cases such as a file with no transcript or the cost/latency of a full fetch, so it stops 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 short sentences with the core capability front-loaded, followed by use cases and then a size warning that routes to cheaper alternatives. Every sentence carries distinct information and nothing is repeated from the schema.

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 two-parameter read tool with no output schema and no annotations, the description covers what is returned, when to prefer it, and the main practical risk (volume). Nothing an agent needs in order to call it correctly appears to be missing.

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 100% and both parameters (file, speaker) are documented in the schema, so the baseline is 3. The description reinforces the default behavior by saying it returns the 'currently playing file', but adds no format or filtering semantics beyond what the schema already states.

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 — 'Return the full transcript of the currently playing file as timed cues' — plus the added return element (provenance/source) and speaker labels. It also implicitly distinguishes itself from the sibling summarisation and search tools, so an agent can identify the tool without opening the 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 explicit positive use cases ('read or summarise a video', 'input for writing your own chapter list with set_chapters') and explicit exclusions with named alternatives ('prefer search_transcript or transcript_summary when you only need a passage or overview'). Both the when and the when-not are covered with concrete conditions.

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