Skip to main content
Glama

graph_get_meeting_recording_url

Retrieves metadata and a temporary download URL for a Microsoft Teams online meeting recording, enabling access to the binary video content for download.

Instructions

Get metadata and download URL for a meeting recording.

Returns recording metadata including a temporary download URL. The recording content itself is binary video and is not returned inline.

Args: meeting_id: The online meeting ID, from graph_get_meeting_id or the id field of graph_list_online_meetings. recording_id: The recording ID (from graph_list_meeting_recordings).

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

Input Schema

NameRequiredDescriptionDefault
meeting_idYes
recording_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and handles the two most important traits: the URL is temporary and the recording binary is not returned inline. Permission requirements and the actual lifetime of the temporary URL are not stated, which keeps it short of a 5.

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 front-loaded sentences state purpose and return shape before the args block; every sentence adds information and nothing is redundant.

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 purpose, return shape, non-returned content, and parameter provenance. It omits error/permission behavior, which is a modest gap rather than a blocking one.

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 coverage is 0%, so the description must supply all parameter meaning, and it does document both parameters with their origin tools, which is more useful than a bare type declaration. It stops short of noting the ID string format or whether a fully qualified path works, so a 4 rather than a 5.

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 ('Get metadata and download URL for a meeting recording') and immediately clarifies the scope of what is returned, distinguishing it from tools like graph_get_transcript_content or graph_get_file_bytes by making clear the binary content is not delivered.

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 the agent a concrete prerequisite chain: meeting_id comes from graph_get_meeting_id or graph_list_online_meetings, and recording_id from graph_list_meeting_recordings. It does not state any when-not-to-use conditions or mention sibling alternatives explicitly, but the workflow guidance is strong for a simple getter.

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