Skip to main content
Glama

graph_list_team_members

Lists members of a Microsoft Teams team with paging support, returning names and roles for a given team ID. Use it after listing teams to inspect who belongs to a team.

Instructions

List members of a team.

Needs the TeamMember.Read.All permission, which requires admin consent.

Args: team_id: The team ID (from graph_list_teams). top: Maximum number of members to return (default 50, maximum 50). 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": {
      "team_id": "<team_id>"
    },
    "name": "graph_list_team_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
team_idYes
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations available, the description carries the full burden and does well: it discloses the required TeamMember.Read.All scope and that admin consent is needed, plus the paging model and how include_next_link changes the response shape. It omits failure behavior (what a 403 or expired next_link looks like), which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line purpose, then a permission caveat, then a clean Args block. Slight redundancy in "default 50, maximum 50" and the default already being in the schema, but nothing wasteful enough to impede reading.

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 paged list tool with no output schema, the description covers auth, paging continuation, and the two possible return shapes, which is most of what a caller needs. It never says what fields a member object contains, leaving the agent to guess between user, group, or device members.

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 largely does: it documents all four parameters, including team_id's provenance, top's default and practical cap, next_link's opaque origin and its precedence over the other paging arguments, and include_next_link's effect on the return shape. The stated maximum of 50 conflicts with the schema's much larger maximum, a small inconsistency a caller could trip over.

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?

"List members of a team" gives a specific verb (list) and a specific resource (team members), which separates it from graph_list_channel_members and graph_list_chat_members by scope alone. It stops short of explicitly naming those siblings or stating what kind of member records come back, so it is clear but not maximally differentiated.

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?

The description implies when to use it (when you have a team ID and want its membership) and helpfully points to graph_list_teams as the source of team_id. It gives no explicit exclusions, no guidance on when to prefer a channel/chat member listing, and no note on what to do if the caller only has a display name rather than an ID.

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