Skip to main content
Glama

List People in Organization

list_users
Read-only

Retrieves users in a Microsoft 365 organization so you can find accounts; limit results, apply OData filters, or fetch all pages.

Instructions

List users in the organization

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
topNoNumber of users (default: 25)
filterNoOData filter expression
fetch_all_pagesNoFetch all pages of results (max 50 pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that the description adds nothing: it says nothing about default page size, the 50-page cap when fetching everything, ordering, or what a returned user contains. For a paginated list tool this is thin.

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, so nothing needs trimming. The tradeoff is that brevity here comes from omission rather than tight packaging of useful detail.

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?

The tool is simple: three optional, fully documented parameters and no output schema, so the schema carries much of the burden. The description still leaves the agent guessing about result scope and paging behavior, which is a clear but not severe gap.

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% (top, filter, fetch_all_pages each documented), so the baseline of 3 applies. The description adds no extra meaning, such as how the OData filter string is scoped to user properties.

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 ("List users") plus a scope ("in the organization"), so the agent knows this returns directory users rather than an arbitrary collection. It does not differentiate from nearby siblings such as list_group_members or list_contacts, which is exactly the 4-level bar.

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?

There is no guidance on when to use this versus alternatives like list_group_members or list_contacts, and no stated prerequisites or exclusions. The agent must infer the organization-directory scope entirely from the word "organization".

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