Skip to main content
Glama

List Meeting Transcripts

list_meeting_transcripts
Read-only

Retrieves transcript IDs for a Teams meeting by meeting_id or join_web_url, giving the identifiers needed to fetch each transcript's content.

Instructions

List the transcripts of a Teams meeting. Identify the meeting by meeting_id, or by join_web_url taken from a calendar event's onlineMeeting.joinUrl. Returns transcript IDs for get_meeting_transcript.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_meeting_transcripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
meeting_idNoOnline meeting ID. Preferred — needs no lookup.
join_web_urlNoTeams join URL (an event's onlineMeeting.joinUrl). Requires the OnlineMeetings.Read scope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint already tells the agent this is a safe read, but the description adds the non-obvious behavioral fact that it returns only IDs rather than transcript text, which shapes how the agent chains calls. It does not discuss empty results or what happens if both identifiers are provided.

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?

Two tight sentences: purpose and identification methods first, follow-up tool second. No filler and nothing that repeats the title verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only list tool with no output schema, the description covers what it returns, how to target the meeting, and which sibling consumes the result. Nothing needed to invoke it correctly 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 coverage is 100% and the schema already explains that meeting_id is preferred and that join_web_url requires OnlineMeetings.Read. The description reinforces the either/or relationship between the two parameters and their source (calendar event's onlineMeeting.joinUrl) but adds little beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("List the transcripts of a Teams meeting") and immediately clarifies the output is transcript IDs, not transcript content. It also distinguishes itself from the sibling get_meeting_transcript by naming it as the consumer of the returned IDs.

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?

It gives clear context: call this to obtain transcript IDs, then use get_meeting_transcript to fetch content. It also states the two ways to identify a meeting. It stops short of explicit when-not-to-use guidance (e.g., behavior when both identifiers are supplied).

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