Skip to main content
Glama

Get a take's transcript

get_transcript
Read-only

A take's words with their indices, kinds (word, filler, pause) and whether each is struck. Struck words appear as i:word in text. Page with offset and 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": {
      "project_id": "<project_id>",
      "take_id": "<take_id>"
    },
    "name": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
take_idYes
project_idYesFrom create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely new behavioral detail — that items are classified by kind and that struck words are rendered inline as ~~i:word~~. That markup convention is something an agent could not infer from the schema and would otherwise misparse, though nothing is said about response envelope, total counts, or error cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what the caller receives before the formatting and paging notes. No filler, though the opening noun fragment ('A take's words...') is slightly cryptic as a lead.

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 does most of the work of conveying return values and does it reasonably (per-word records, kind enumeration, struck markup). It leaves gaps on the overall response shape and on take_id/project_id identification, which matter for a 4-parameter read tool.

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 coverage is only 25% (only project_id has a description, 'From create_project'), so the description must compensate. It does explain offset and limit as the paging controls, but take_id and project_id semantics are left to the schema, and the defaults (600/1500 cap) are only visible in the schema, not reinforced.

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 ('a take's words') and enumerates exactly what each item carries: indices, kinds (word, filler, pause), and struck status. That is specific enough to distinguish a read of transcript content from a sibling like edit_transcript, but the tool does not explicitly contrast itself with any alternative, so it stops short of a 5.

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?

'Page with offset and limit' gives real operational guidance for large transcripts, but there is no statement of when to call this versus edit_transcript or export_subtitles, and no prerequisites (e.g., needing a valid take_id from a project). Usage is implied rather than prescribed.

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.

Resources