Skip to main content
Glama
Sign In
notion-mpm

notion-mpm

by bobmatnyc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_users

List all users in a Notion workspace. Use page_size and start_cursor to paginate through large user lists.

Instructions

List all users in the Notion workspace.

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
page_sizeNoMaximum number of users to return (max 100)
start_cursorNoPagination cursor from a previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

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 burden. It claims to list 'all' users but does not disclose that results are paginated (max 100 per page via page_size), nor does it mention authentication needs or response format, creating potential for misinterpretation.

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?

The description is a single concise, front-loaded sentence with zero wasted words. It immediately communicates the core action.

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 list tool with a well-documented schema, the description is minimally viable. However, without an output schema or annotations, it could provide more context about pagination to truly retrieve 'all' users, as the current wording may imply a single unfiltered list.

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?

The input schema provides complete descriptions for both parameters (page_size with max 100, start_cursor as a pagination token). Since schema coverage is 100%, the description does not need to add parameter details, and the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'list' and resource 'users' within the 'Notion workspace', providing a specific and unambiguous purpose. It naturally distinguishes itself from singular tools like get_user and get_bot_user.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_user or search. While the function is obvious from the name, there is no explicit mention of selection criteria or exclusions.

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