Enterprise Microsoft 365 MCP Server

Overview Schema Source Related Servers Discussions Admin

m365_get_group_members

Retrieve the member list of a distribution group to audit membership, verify recipients, or manage access in Exchange Online and Microsoft 365.

Instructions

Retrieves the member list of a distribution group.

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": {
      "group_identity": "<group_identity>"
    },
    "name": "m365_get_group_members"
  }
}

Input Schema

Name	Required	Description	Default
`group_identity`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 29, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. Beyond 'retrieves', it says nothing about permissions required, behavior for large groups (pagination/truncation), transitive vs direct members, or error cases for an unknown group — all relevant for a directory read on groups that can have thousands of members.

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?

A single short sentence with no filler and the object front-loaded. It is efficient, though the brevity comes at the cost of the missing detail noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. For a one-parameter read tool this is close to adequate, but the identity format and group-size behavior remain undocumented, leaving a real gap an agent could stumble on.

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

Parameters2/5

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

Schema description coverage is 0%, and the single parameter group_identity has no title-level explanation of accepted value forms (GUID, SMTP address, display name). The description narrows the target to a distribution group, which is marginal added meaning but does not compensate for the format ambiguity.

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?

States a specific verb (Retrieves) and resource (member list of a distribution group), so an agent can tell it apart from m365_list_distribution_groups and m365_manage_group_member by object and scope. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiating.

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

Usage Guidelines2/5

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

No indication of when to use this tool versus m365_list_distribution_groups or m365_manage_group_member, and no prerequisites or context are given. The implied usage (read a group's membership) is inferable from the verb, but nothing is stated.

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

Deploy Server