Skip to main content
Glama

graph_list_meeting_transcripts

Fetch available transcripts for an online meeting using its meeting ID; optionally page through results with next-link support.

Instructions

List available transcripts for an online meeting.

Args: meeting_id: The online meeting ID, from graph_get_meeting_id or the id field of graph_list_online_meetings. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

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>"
    },
    "name": "graph_list_meeting_transcripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
next_linkNo
meeting_idYes
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavior: include_next_link defaults to false and returns a bare list, true wraps as {items, next_link}, and next_link overrides the other paging arguments. It says nothing about permissions, transcript availability/consent requirements, or error behavior.

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?

Front-loaded one-sentence purpose followed by a compact Args block; each parameter note carries information not in the schema. The docstring formatting is slightly verbose but no sentence is wasted.

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 three-parameter list operation with no output schema and no annotations, the definition covers the essentials: purpose, ID provenance, and the paging/return-shape contract. Remaining gaps — auth scope and error conditions — are secondary.

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: all three parameters are explained, including where meeting_id comes from, the opacity of next_link, and exactly what include_next_link changes about the return shape. Only the format of meeting_id is left unspecified.

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 first line gives a specific verb and resource — 'List available transcripts for an online meeting' — which separates it from graph_list_meeting_recordings and graph_get_meeting_recording_url by resource type. It does not explicitly name those siblings as alternatives, but the operation itself is unambiguous.

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 context is implied rather than stated: the meeting_id doc points the agent to graph_get_meeting_id or graph_list_online_meetings to obtain the ID, which is a useful routing hint. There is no explicit 'use this instead of / before that' guidance and no prerequisite or exclusion statements.

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