Skip to main content
Glama

Read a transcript

get_transcript
Read-onlyIdempotent

Retrieve meeting transcripts with timestamps and speaker names to verify exact wording, quotes, and context. Read long recordings in timed segments using start and end points.

Instructions

The transcript turn by turn: "[time] Name: text". For exact wording and context: "What exactly did Priya say about the deadline?", "Quote the client's objection". Read a long meeting (an hour is about 60,000 characters) in pieces around the place search pointed to. Read-only.

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": {
      "meeting": "<meeting>"
    },
    "name": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoWhere in the recording to stop; empty — to the end
startNoWhere in the recording to start: 12:30 or 1:02:03; empty — from the beginning
meetingYesMeeting id from search or list_meetings

Output Schema

NameRequiredDescriptionDefault
resultYes

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 declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the output line format, a size estimate (an hour is ~60,000 characters), and the recommendation to page through long meetings rather than fetch everything at once.

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

Conciseness3/5

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

The core information is front-loaded, but the opening sentence is awkwardly constructed with nested quoting ('The transcript turn by turn: "[time] Name: text".'), and the two example queries convey largely the same point, adding redundancy rather than new signal.

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?

With an output schema present the description need not explain return values further, and it still covers format, size, and paging strategy. The one gap is the absence of guidance on what happens when the meeting id is invalid or the range is out of bounds, but overall an agent has enough to call it correctly.

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 100%, so start, end, and meeting are already documented with formats and defaults, making 3 the baseline. The description adds only indirect meaning, motivating start/end as the chunking mechanism for long transcripts, without new syntax or edge-case guidance.

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?

States a specific verb+resource (read a transcript) and pins down the returned shape as '[time] Name: text' turn by turn. It also anchors the tool relative to search by telling the agent to page 'around the place search pointed to', though it never explicitly contrasts with get_meeting or list_meetings.

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?

Gives concrete usage triggers via example asks ('What exactly did Priya say about the deadline?', 'Quote the client's objection') and implies it follows a search call when reading a long meeting in pieces. It lacks an explicit exclusion such as 'use get_meeting for metadata/summary', so the boundary against siblings is only implied.

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