Skip to main content
Glama

transcript_get

Read-only

Retrieve an asset's transcript as numbered, time-stamped sentences so you can use sentence IDs or timestamps for clip in/out points; request per-word timing with the words format.

Instructions

Read an asset's transcript as numbered sentences with times: [s0012 03:41.2–03:47.9] text. Use sentence ids in clips ({sentences:{from,to}}) or the times as in/out. format 'words' gives per-word times.

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": {
      "assetId": "<assetId>"
    },
    "name": "transcript_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
pageNo
startNo
formatNocompact
assetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true is already supplied by annotations, so the safety profile is covered; the description adds the sentence-id scheme and the per-word times mode, which is real added context. It is silent on pagination behavior, transcripts that don't exist yet, and how start/end filtering affects returned sentence numbering.

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 return shape and then the two follow-on uses. Every clause carries information; nothing is padding.

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?

With no output schema, the description correctly spends its space on the return format, which is the most important gap filled. However, a five-parameter tool with a 'page' parameter and time-range filters is left unexplained, and no error/empty-transcript behavior is mentioned.

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% for five parameters, so the description carries the full burden and largely doesn't. It hints at the 'format' enum ('words' gives per-word times) but never explains assetId, page, or start/end, and the 'in/out' reference points at another tool's parameters rather than this tool's start/end.

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 ('Read an asset's transcript') and goes further by showing the literal output shape '[s0012 03:41.2–03:47.9] text'. No sibling is named, but 'transcript' is unambiguous against frames_get, timeline_get and analysis_get, so an agent can route correctly.

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?

Usage guidance is about consuming the output ('Use sentence ids in clips ({sentences:{from,to}}) or the times as in/out') rather than when to call this tool versus a sibling. That downstream hint is genuinely useful, but there is no explicit when-to-use or when-not-to-use statement.

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