Skip to main content
Glama
adkins-amdg

Microsoft Teams MCP Server

by adkins-amdg

List Team members

teams_list_team_members
Read-onlyIdempotent

Retrieve a list of team members with their roles (e.g., owner) for any Microsoft Teams team. Specify team ID, limit (1-50), and output format (markdown or JSON).

Instructions

List members of a team, including their roles (e.g. 'owner').

Note: requires the delegated scope TeamMember.Read.All, which may need a one-time Entra admin consent.

Args:

  • team_id (string): the team ID

  • limit (number, 1-50): max members (default 20)

  • response_format ('markdown' | 'json'): output format (default markdown)

Returns: JSON { count, members: [{ id, displayName, email, roles }] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return (1-50)
team_idYesThe Microsoft Teams team (group) ID. Get it from teams_list_joined_teams.
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Discloses required scope and admin consent, and return structure beyond annotations. Annotations already indicate read-only and idempotent; description adds permission context.

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?

Concise, front-loaded purpose, and includes needed details. The note on scope is slightly secondary but overall efficient.

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?

Covers purpose, permissions, parameters (with defaults), and return structure. Adequate for a simple list tool with no output schema.

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

Parameters3/5

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

Schema coverage is 100%, and description repeats schema documentation without adding new meaning. The cross-reference to get team_id is already in 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?

Clearly states it lists team members with roles. Distinct from sibling tools like teams_list_channels or teams_create_meeting.

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?

Provides permission requirements (scope and admin consent) but does not explicitly guide when to use this tool versus alternatives among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adkins-amdg/teams-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server