Skip to main content
Glama

get_transcription

Read-only

Retrieve a clip’s transcription, including language, speaker segments, timing, and words. Run analyze_media(action='transcribe') first.

Instructions

Transcription of a clip (language, segments with speaker, timing and words). Run analyze_media(action='transcribe') first.

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": {
      "clip": "<clip>"
    },
    "name": "get_transcription"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
nestedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the bar is lower, yet the description adds a genuinely non-obvious behavioral fact: the transcription is not computed on demand and depends on a prior analyze_media(action='transcribe') run. It does not say how a missing transcription is surfaced (error vs. empty result), which is the main remaining gap.

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?

Two compact sentences: the first front-loads the payload contents in a parenthetical, the second front-loads the prerequisite. Every clause carries information and there is no filler.

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?

For a two-parameter read tool with no output schema, the parenthetical inventory of returned fields usefully substitutes for a return-value description, and the prerequisite is stated. The only shortfall is the unexplained 'nested' flag, which is the one thing an agent cannot infer from anything else in the definition.

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 carry the burden and it largely does not. It never mentions the required 'clip' argument or what form a clip identifier takes, and the 'nested' boolean is completely unaddressed, leaving the agent to guess its effect on the returned segment structure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (transcription of a clip) and enumerates what the result contains: language, speaker-tagged segments, timing and words. That is specific enough to distinguish it from generic siblings like get_clip, though the retrieval verb itself is only implied by the tool name.

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?

It gives an explicit prerequisite ordering: run analyze_media(action='transcribe') first, which tells the agent this is a follow-up read rather than a standalone call. It stops short of naming an alternative or stating what happens when the prerequisite has not been satisfied, so it is not fully exhaustive.

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