Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

list_group_members

Retrieve every member of a Microsoft 365 Group to find their email addresses before sending a message. Supports filtering, search, and property selection to narrow results.

Instructions

List all members of a Microsoft 365 Group. Useful for finding email addresses of everyone in a group before sending.

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": {
      "groupId": "<groupId>"
    },
    "name": "list_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of members to return (default: 100, max: 999)
filterNoOData filter expression (e.g. "displayName eq 'Jane Doe'")
searchNoSearch string for displayName (e.g. 'Jane')
selectNoComma-separated properties to return (e.g. 'id,displayName,mail')
groupIdYesThe Microsoft 365 Group ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 disclosure burden. It implies a read-only listing, but says nothing about pagination behavior, result limits, permissions required, or what happens when a group has more members than the returned page — gaps left entirely to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two short sentences with zero filler; the core action is front-loaded and the use case follows immediately. Nothing would be lost by keeping it exactly this length.

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?

For a simple five-parameter read tool with full schema coverage this is close to adequate, but the absence of annotations means the definition should at least note that results are paged and that the default page size is finite, which it does not.

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 description coverage is 100%, with every parameter (top, filter, search, select, groupId) documented in the schema itself, so the baseline is 3. The description adds no additional meaning about how filtering, searching, or selecting interact with group membership.

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 and resource: "List all members of a Microsoft 365 Group." This clearly separates it from siblings like list_users or list_contacts, though it does not explicitly distinguish against list_distribution_groups, which an agent could reasonably confuse it with.

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 one usage scenario ("finding email addresses of everyone in a group before sending"), which implies when to reach for it. There is no explicit when-not guidance and no named alternative such as list_distribution_groups, so the agent must infer selection.

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