Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

list_users

Search Azure AD users by name or email to find recipient addresses, or list all organisation users with pagination controls.

Instructions

Search or list Azure AD users in the organisation. Use 'search' to find users by name or email. Without 'search', returns all users paginated. Useful for finding recipient email addresses.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of users to return (default: 50, max: 999)
skipNoNumber of users to skip (for pagination)
searchNoSearch string to filter users by display name or email
selectNoComma-separated properties to return (default: id,displayName,mail,userPrincipalName)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the search-vs-list mode and that unfiltered results are paginated, but it does not mention required permissions, result ordering, or other operational constraints.

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?

Three short sentences are front-loaded with the core action and mode distinction. Each sentence adds useful context without unnecessary wording.

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?

This is a simple read/list tool with fully documented parameters and no output schema. The description covers the main modes and intended use, though it omits some behavioral details that would be useful in the absence of annotations.

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%, so the schema already documents top, skip, search, and select. The description reinforces the search behavior and pagination but adds little parameter-level meaning beyond what the schema provides.

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?

The description states a specific verb and resource: search or list Azure AD users in the organisation, and notes the recipient-email use case. It is clear what the tool does, but it does not explicitly distinguish itself from nearby siblings such as list_contacts or list_distribution_groups.

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 clear operational context: use 'search' to find users by name or email, and omit 'search' to return the paginated full list. It also names a practical use case, finding recipient email addresses, though it does not explicitly state when to choose this tool over sibling listing tools.

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