Skip to main content
Glama

graph_get_meeting_attendance

Retrieve Microsoft Teams meeting attendance reports to see who joined, when they joined or left, and how long they stayed; list available reports or expand one by report ID.

Instructions

Get meeting attendance: who actually joined and for how long.

Without report_id this lists the available attendance reports. With report_id it returns that report expanded with per-attendee join and leave times, and the paging arguments do not apply. Needs the OnlineMeetingArtifact.Read.All permission, which requires admin consent.

Args: meeting_id: The online meeting ID, from graph_get_meeting_id or the id field of graph_list_online_meetings. report_id: Attendance report ID. Empty lists the available reports. 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_get_meeting_attendance"
  }
}

Input Schema

NameRequiredDescriptionDefault
next_linkNo
report_idNo
meeting_idYes
include_next_linkNo

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 burden and does well: it discloses the required permission OnlineMeetingArtifact.Read.All and that admin consent is needed, which is an invocation-blocking prerequisite. It also explains the result-shape switch (include_next_link=true wraps as {items, next_link}, default false returns a bare list) and that next_link overrides the other paging arguments. Failure modes and rate limiting are not covered, keeping it below 5.

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?

Front-loaded with the core purpose, then mode logic, then a tidy Args block, so structure is easy to scan. There is mild redundancy: the prose already says 'Without report_id this lists the available attendance reports' and the Args entry repeats 'Empty lists the available reports', which could be collapsed without losing information.

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 four-parameter tool with no annotations and no output schema, the definition covers the essentials: auth requirements, both operating modes, paging control, and the two possible return shapes. What is missing is any sense of the per-attendee fields returned or how an absent/empty report is signaled, which an agent might want when deciding whether this tool answers its question.

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%, so the description must compensate entirely, and it does: every one of the four parameters is explained with meaning beyond its name. meeting_id gains provenance, report_id gains the 'empty means list' semantics, next_link is identified as an opaque URL from a prior call that overrides other paging args, and include_next_link's default and effect on return shape are spelled out.

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 opening line names a specific verb and resource ('Get meeting attendance') and immediately scopes it with 'who actually joined and for how long', which separates it from recording- or transcript-oriented siblings. The two-mode behavior (list reports vs. expanded report) is stated in the same breath, so an agent knows exactly what it retrieves.

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 an explicit decision rule between the tool's two modes: without report_id you get the list of available reports, with report_id you get the expanded per-attendee detail. It also routes the agent to graph_get_meeting_id or graph_list_online_meetings for the meeting_id. It stops short of saying when to prefer this over related siblings such as transcript or recording tools.

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