Skip to main content
Glama

graph_list_meeting_recordings

List available recordings for a Microsoft Teams online meeting so you can find and access meeting media for review or sharing.

Instructions

List available recordings 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_recordings"
  }
}

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.5/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 useful behavior: include_next_link defaults to false and returns a bare list, while next_link is an opaque URL that overrides the other paging arguments. It says nothing about access requirements for recordings (commonly permission-restricted in Graph) or what happens when no recordings exist, so an agent could still be surprised.

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?

The purpose sentence is front-loaded and each arg entry earns its place with no filler. The Args block mirrors a docstring but stays short and scannable.

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

Completeness3/5

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

For a three-parameter list tool with no annotations and no output schema, the description covers inputs and paging well but leaves the recording object's contents and permission requirements undocumented. An agent can call it correctly, but may not know what it gets back or why a call might fail.

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, what next_link is and its precedence over other paging args, and the exact result shape controlled by include_next_link. Only the format of the opaque next_link and validation of meeting_id are left unstated.

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 sentence gives a specific verb and resource: list recordings for an online meeting. That is clearly distinct from siblings like graph_list_meeting_transcripts or graph_get_meeting_recording_url by resource type, though the description never explicitly contrasts them.

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 is implied by 'for an online meeting', and the meeting_id arg points to graph_get_meeting_id or graph_list_online_meetings as the source, which helps an agent get started. However, there is no statement of when to prefer this over graph_get_meeting_recording_url or graph_list_meeting_transcripts, and no preconditions or exclusions.

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