Skip to main content
Glama
Sign In
Microsoft Graph MCP Server

Microsoft Graph MCP Server

by ry-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_users

Retrieve users in a Microsoft 365 tenant through Microsoft Graph, with an optional result limit, to support administration, provisioning, and directory management workflows.

Instructions

List all users in the tenant

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not say this is a read-only operation, whether it requires tenant admin rights, or that results are capped at the 'top' default of 100. For a paginated enumeration endpoint, silent truncation is exactly the behavior an agent needs disclosed.

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 front-loaded sentence with no wasted words. It is efficient but arguably under-sized given the tool's unstated pagination behavior, which lands it just below the top mark.

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 no-annotation read tool with a fully described schema and no output schema, the description is minimally adequate. It omits result-truncation behavior, ordering, and the distinction from search_user, which an agent needs to call it correctly.

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 the single 'top' parameter is fully documented in the schema, so the baseline is 3. The description adds no semantics about paging behavior or what happens when more users exist than 'top'.

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 (List) and resource (users) plus scope (in the tenant), which separates it from get_user or create_user at a glance. It does not explicitly differentiate from search_user, which is the sibling an agent is most likely to 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 Guidelines2/5

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

No guidance on when to use this versus search_user for filtered lookups, and no prerequisites or exclusions are given. The only hint is the word 'all', which implies unfiltered enumeration but is never stated as a rule.

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