Skip to main content
Glama

graph_get_transcript_content

Retrieve a meeting transcript's text content in VTT format, including timestamps and speaker attribution, using meeting and transcript IDs.

Instructions

Get the text content of a meeting transcript.

Returns the transcript in VTT (Web Video Text Tracks) format, which includes timestamps and speaker attribution.

Args: meeting_id: The online meeting ID, from graph_get_meeting_id or the id field of graph_list_online_meetings. transcript_id: The transcript ID (from graph_list_meeting_transcripts).

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_id": "<meeting_id>",
      "transcript_id": "<transcript_id>"
    },
    "name": "graph_get_transcript_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
meeting_idYes
transcript_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden. It does disclose the return format (VTT with timestamps and speaker attribution), which is valuable, but says nothing about permission scopes, throttling, transcript availability delays, or size limits for long meetings.

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 blocks: purpose, return format, then args. The return format is front-loaded right after the verb, and every line adds information an agent would otherwise have to guess.

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 and no annotations, the description covers what is returned and where inputs come from. The remaining gap is operational behavior—auth requirements and handling of large or unavailable transcripts—which nothing else in the structured fields supplies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 compensate, and it does: both parameters are explained along with their provenance. It stops short of 5 because it doesn't state the ID format (GUID vs. joinable string) or whether IDs from different sources are interchangeable.

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 opens with a specific verb+resource: 'Get the text content of a meeting transcript,' which naturally separates it from graph_list_meeting_transcripts (listing) and metadata-oriented siblings. It does not explicitly name a sibling to route away from, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is made concrete through prerequisite chaining: meeting_id comes from graph_get_meeting_id or graph_list_online_meetings, and transcript_id from graph_list_meeting_transcripts. That tells an agent exactly how to reach a callable state, though it gives no explicit when-not-to-use or alternative retrieval path (e.g. file content).

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