Skip to main content
Glama

transcript

Retrieve a media clip's timed speech-to-text segments in source seconds for clip assembly, with optional word-level timings; automatically generates text when missing.

Instructions

Get the transcription of a media clip as segments with start/end in SECONDS OF SOURCE (ready for clips_assemble in/out). words=true includes word-level timings. Transcribes first if needed.

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": {
      "item": "<item>"
    },
    "name": "transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
wordsNo
transcribe_if_missingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a meaningful side effect: 'Transcribes first if needed' means this call can trigger expensive transcription work. It does not say whether that work is synchronous, how long it takes, whether it costs credits, or what happens if transcription fails — notable gaps for a no-annotation tool.

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, front-loaded with the most important detail (SECONDS OF SOURCE) that distinguishes the output from other time units. No filler; every clause carries information.

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

Completeness3/5

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

For a three-parameter, no-annotation, no-output-schema tool, the description should explain the input identifier and the full return shape. It describes segments partially but omits the overall response structure (is there a full text field?) and leaves the required 'item' parameter undefined.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain all three parameters. It covers only 'words' clearly (word-level timings) and gestures at 'transcribe_if_missing' via 'Transcribes first if needed,' without naming the parameter or saying what false does. The required 'item' parameter is never explained (clip ID? path? object?).

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 ('Get the transcription of a media clip') plus the concrete return shape (segments with start/end in seconds of source). It also names the downstream consumer (clips_assemble in/out), so an agent can place it in the workflow without opening a schema.

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

Usage Guidelines3/5

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

The reference to clips_assemble implies this is the step that produces usable in/out points, which gives contextual usage. However, there is no explicit when-to-use/when-not guidance, no statement of what to do if the clip already has a transcript, and no comparison to any other inspection sibling.

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