Skip to main content
Glama
Sign In
notion-mcp

notion-mcp

by snickery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

notion_list_users

List users in a Notion workspace to retrieve names, IDs, emails, and types, with an optional name filter for finding user IDs needed in people properties and @mentions.

Instructions

List all users in the Notion workspace.

Returns user names, IDs, emails, and types (person or bot). User IDs are needed for people properties and @mentions in comments.

name_contains: optional case-insensitive filter on the user's name.

Input Schema

NameRequiredDescriptionDefault
name_containsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / name_contains
      Added value: +{
+  "default": "",
+  "title": "Name Contains",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses return fields and user types (person or bot), but does not mention pagination, permissions, or whether all workspace users are always returned.

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 front-loaded with the core action and return fields, then adds the practical use case and the optional filter. Every sentence contributes useful context without bloat.

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 simple one-parameter list tool with an output schema, the description covers purpose, return values, use case, and parameter behavior. Missing pagination and permission details are minor given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates by explaining the only parameter: name_contains is optional and applies a case-insensitive filter on the user's name. It could clarify substring vs. exact matching, but the core semantics are covered.

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 uses a specific verb and resource ('List all users') and scopes it to the Notion workspace, while also naming returned fields. It does not explicitly distinguish this list operation from the sibling notion_get_user tool, so it falls short of a 5.

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?

It gives a clear use case: user IDs are needed for people properties and @mentions in comments. However, it does not explicitly say when to use notion_get_user instead, so there is no sibling routing guidance.

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