List users in a Notion workspace with optional page size and pagination cursor. Retrieve user objects for workspace membership or mention handling.
List all users in the workspace.
Args: page_size: Number of results per page (max 100) start_cursor: Cursor for pagination
Returns: List of user objects
| Name | Required | Description | Default |
|---|---|---|---|
| page_size | No | ||
| start_cursor | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses scope ('workspace') and return type, but says nothing about permissions required, whether pagination terminates, result ordering, or rate limits for an operation that enumerates all users.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loads the one-line purpose and uses an Args/Returns layout that is easy to scan. No wasted sentences, though the Returns block is redundant with the existing output schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers both parameters and the operation's scope, and the output schema handles return values, so the core is present. It still lacks the pagination loop semantics and any access requirements that an agent enumerating an entire workspace would want.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds a meaningful constraint ('max 100') and clarifies start_cursor is for pagination, but omits the default values and does not explain that start_cursor is null-typed on the first call.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource with scope: 'List all users in the workspace.' An agent can distinguish it from the singular get_user and get_self siblings, though the description never explicitly contrasts them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus alternatives like get_user (single user) or get_self (current user), nor any prerequisites for listing the full workspace directory. Usage must be inferred from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.