Skip to main content
Glama

mcp-notion__notion-get-users

Read-onlyIdempotent

Retrieves a list of users in the current workspace. Shows workspace members and guests with their IDs, names, emails (if available), and types (person or bot).

Supports cursor-based pagination to iterate through all users in the workspace.

  1. Search for users by name or email: {"query": "john"}

  2. Get next page of results: {"start_cursor": "abc123"}

  3. Set custom page size: {"page_size": 20}

  4. Fetch a specific user by ID: {"user_id": "00000000-0000-4000-8000-000000000000"}

  5. Fetch the current user: {"user_id": "self"} Through Royally: its server marks it read-only, so it runs straight away.

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": "mcp-notion__notion-get-users"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional search query to filter users by name or email (case-insensitive).
skillNoFor tracking only: the name of the agent skill you are following for this task, such as notion-meeting-prep. Omit if you are not following a skill.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
user_idNoReturn only the user matching this ID. Pass "self" to fetch the current user.
page_sizeNoNumber of users to return per page (1–100; default 100).
start_cursorNoCursor for pagination. Use the next_cursor value from the previous response to get the next page.
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the final sentence ("its server marks it read-only, so it runs straight away") merely restates that, in garbled form, adding no new information. The genuinely additive behavior is the description of pagination via cursor and the enumeration of returned fields, which is real value given there is no output schema.

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?

Purpose and pagination are front-loaded in two tight sentences, and the examples are compact and scannable. The trailing clause "Through Royally: its server marks it read-only, so it runs straight away." is stray, unexplained noise that does not earn its place.

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?

For a 7-parameter, zero-required read tool with no output schema, the description covers what comes back and how to iterate pages, which is the information an agent actually needs. Bookkeeping parameters (skill, site_id, instructions_version) are left to the schema, which is reasonable since they are documented there.

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 query, user_id (including "self"), page_size, and start_cursor are all documented in the schema itself. The examples restate those same meanings in call form rather than adding syntax, defaults, or interaction semantics, so the baseline of 3 applies.

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 ("Retrieves a list of users in the current workspace") and enumerates the returned fields (IDs, names, emails, person/bot types), so the agent knows exactly what the call yields. It does not differentiate from near-neighbors such as notion-get-self or notion-get-groups, even though the "user_id: self" example silently overlaps with the former.

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?

The six examples effectively show the main call modes: unfiltered listing, filtered search, cursor pagination, custom page size, and single-user fetch. Context is clear, but there is no explicit when-not guidance or named alternative for the overlapping single-user case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources