Skip to main content
Glama

graph_list_online_meetings

Look up a Microsoft Teams online meeting by join URL or numeric meeting ID, returning the matching meeting record and optional paging link.

Instructions

Look up an online meeting by join URL or by the numeric meeting ID.

Microsoft Graph has no unfiltered list of online meetings, so exactly one of join_url or join_meeting_id is required; without one the request fails with "One of the required parameters to lookup meeting by QueryOptions is null or empty". Either lookup returns a collection holding at most one meeting. When you only have a calendar event or a meeting chat thread, call graph_get_meeting_id.

Args: join_url: Teams meeting join URL, passed exactly as Graph reports it in onlineMeeting.joinUrl. Empty to look up by join_meeting_id. join_meeting_id: The numeric meeting ID printed in the invite, with or without spaces (for example "359 232 213 325 013"). Empty to look up by join_url. 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

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_list_online_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
join_urlNo
next_linkNo
join_meeting_idNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.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 behavioral burden and does well on the important parts: no unfiltered listing exists, the result is a collection of at most one meeting, and paging wraps output when include_next_link is set. It does not disclose required permissions/scopes or who can see which meetings, and it never says what happens when the lookup finds nothing, so a mutation-free but auth-sensitive lookup is only partly covered.

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 behavioral constraints are front-loaded ahead of the Args block, which is the right order. Some padding remains — the quoted error string and the repeated 'Empty to look up by ...' phrasing on both key parameters restate the single 'exactly one of' rule — but nothing is misleading.

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 four-parameter lookup with no annotations and no output schema, the description supplies the requirement rule, the failure mode, the return cardinality and shape, paging continuation, and the sibling to use when lookup keys are missing. An agent has everything needed to call it correctly on the first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet all four parameters are explained with meaning and operational detail: join_url must be passed exactly as Graph reports it in onlineMeeting.joinUrl, join_meeting_id accepts the invite ID with or without spaces (example given), next_link overrides other paging arguments, and include_next_link changes the return shape with an explicit default. This fully compensates for the empty schema.

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 first sentence gives a specific verb (look up) and resource (online meeting) plus the two lookup keys, and the second sentence immediately corrects the misleading 'list' in the tool name by stating Graph has no unfiltered list. It also names the sibling graph_get_meeting_id as the route when only an event or chat thread is in hand, so an agent can place it among the other graph_* meeting tools without reading schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states an explicit precondition (exactly one of join_url or join_meeting_id is required), quotes the Graph error returned when neither is supplied, and routes the agent to graph_get_meeting_id when it lacks either key. Both the when-to-use and the when-not-to-use case are covered.

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