Skip to main content
Glama

graph_get_meeting_id

Resolves the online meeting ID required by other meeting tools from a calendar event, Teams join URL, or chat thread, adding a thread-based fallback when the join URL lookup returns no result.

Instructions

Resolve the online meeting ID that the other meeting tools require.

Takes a calendar event, a Teams join URL, or a meeting chat thread and returns the ID used by graph_get_online_meeting, graph_list_meeting_transcripts, graph_get_transcript_content, graph_list_meeting_recordings, graph_get_meeting_recording_url and graph_get_meeting_attendance. It prefers the join URL lookup Graph documents and, when that finds nothing, derives the ID from the meeting thread and organizer instead, so it still answers for meetings the lookup misses. The returned "source" says which route produced the ID.

Only meetings the signed-in user organized are reachable through the delegated meeting tools, whoever owns the calendar item.

Args: event_id: Calendar event ID to resolve. Empty to use join_url or thread_id. join_url: Teams meeting join URL to resolve. Empty to use event_id or thread_id. thread_id: Meeting chat thread ID such as "19:meeting_@thread.v2". Empty to use event_id or join_url. organizer_id: The organizer's Microsoft Entra object ID. Used only with thread_id; empty resolves the signed-in user.

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": "graph_get_meeting_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idNo
join_urlNo
thread_idNo
organizer_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses important behavior: join URL lookup is preferred, thread/organizer fallback is used when lookup misses, and the returned "source" identifies the resolution route. It also states the delegated-tool access constraint. It does not describe failure behavior or precedence when multiple inputs are supplied.

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 description is front-loaded with the core purpose and then provides structured fallback, access, and argument details. The list of downstream tools is somewhat long but relevant to purpose. Overall it is clear and mostly earns its length.

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 resolver tool with four optional parameters, no annotations, and no output schema, the description is quite complete: it covers accepted input forms, fallback behavior, return source, and a key permission constraint. It still lacks explicit error conditions and precedence when multiple inputs are provided.

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 substantially does by explaining each of the four parameters and how empty values allow fallback to the others. It also gives a thread_id format example and identifies organizer_id as an Entra object ID. It leaves ambiguity about what happens if multiple non-empty identifiers are passed or if all are empty.

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 uses a specific verb and resource: "Resolve the online meeting ID." It explicitly positions the tool as a prerequisite for named downstream meeting tools, making its role distinguishable from siblings such as graph_get_online_meeting and graph_list_meeting_transcripts.

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 clearly states when the tool is needed: whenever another meeting tool requires the online meeting ID. It also constrains usage to meetings organized by the signed-in user. However, it does not explicitly say when to skip this tool, such as calling graph_get_online_meeting directly when an ID is already known.

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