Skip to main content
Glama

Read Meeting Transcript

get_meeting_transcript
Read-only

Retrieves a Teams meeting transcript as timestamped WebVTT text, with speaker attribution when available, using a transcript ID from a meeting. Works for any attendee, not only the organizer.

Instructions

Get the text of one Teams meeting transcript, as timestamped WebVTT utterances. Works for attendees, not just the organizer. Falls back to a speaker-less transcript automatically when the tenant has speaker attribution disabled.

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": {
      "transcript_id": "<transcript_id>"
    },
    "name": "get_meeting_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoCharacter position to start from (default: 0). When the output ends with a truncation marker, call again with the offset it names to get the next part.
max_charsNoReturn at most this many characters per call (default: 50000)
meeting_idNoOnline meeting ID. Preferred — needs no lookup.
join_web_urlNoTeams join URL, as an alternative to meeting_id. Requires the OnlineMeetings.Read scope.
transcript_idYesTranscript ID from list_meeting_transcripts
include_speaker_namesNoAsk for speaker-attributed text (default: true). Ignored if the tenant disallows it.

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 only declare readOnlyHint=true, and the description adds genuinely new behavior: attendee-level access and an automatic silent fallback to a speaker-less transcript when tenant attribution is disabled. That fallback disclosure is important because it explains an output shape the caller did not request and would otherwise look like a bug.

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 tight sentences, front-loaded with what the tool returns, followed by access scope and the fallback caveat. No filler or restatement of the title.

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 no output schema, the description usefully characterizes the return value as timestamped WebVTT utterances, and the truncation/pagination contract is carried by the parameter schema. Some detail on what a speaker-less transcript looks like is left implicit, but nothing critical for correct invocation is missing.

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 description coverage is 100%, so all six parameters (including the offset/truncation loop and include_speaker_names) are already documented with defaults and constraints. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 and resource (get the text of one Teams meeting transcript) plus the return format (timestamped WebVTT utterances), which lets an agent distinguish it from list_meeting_transcripts by the singular scope. It does not name that sibling explicitly in the description body, so the differentiation is implied rather than stated.

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 note that it 'works for attendees, not just the organizer' gives useful authorization context for selecting this tool, but there is no explicit when-to-use/when-not comparison against alternatives such as list_meeting_transcripts. The sequencing hint ('Transcript ID from list_meeting_transcripts') appears only in the schema, not the description.

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