Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

notion-mcp__notion_list_users

Read-only

Lists the people and bots in the Notion workspace, or reads one of them. Each user is reduced to id, type (person or bot), name, and email for a person when Notion includes it; a bot also carries workspace_name. With user_id set to "me", returns the DataToRAG connection's own bot user, whose workspace_name names the workspace this connection is in. The result is {results, has_more, next_cursor}, with the same shape when there are no results. has_more true means more results exist than this page holds, and next_cursor is the cursor argument that returns them. A single user comes back in the same shape, as a one-item results list.

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": "notion-mcp__notion_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoThe next_cursor value from an earlier call with the same arguments. Returns the page of results after that one. Absent for the start of the list.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
user_idNoA Notion user id, with or without dashes, or "me" for the connection's own bot user. Absent lists the workspace.
page_sizeNoHow many results one call returns, from 1 to 100. Default 50. A full page comes back with has_more true and a next_cursor for the rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description goes well beyond that by specifying the reduced field set returned per user (id, type, name, email, workspace_name for bots), the full response envelope {results, has_more, next_cursor}, the meaning of has_more and next_cursor, and the edge case that an empty result keeps the same shape. That is exactly the behavioral context an agent needs for a tool with 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?

Front-loaded with purpose, then result shape, then pagination semantics — a sensible order with no filler sentences. There is minor redundancy: the pagination contract is restated in the single-user sentence, and the envelope shape is explained twice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter, read-only, no-output-schema tool, the description covers mode selection, field-level return contents, envelope shape, pagination, and the empty-result case. An agent can call it and interpret the response without additional assumptions.

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 coverage is 100%, so the baseline is 3; the description earns more by explaining that a "me" user_id resolves to the DataToRAG connection's own bot and that its workspace_name identifies the current workspace, which the schema only gestures at. It adds little for cursor and page_size beyond what the schema already documents.

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?

States a specific verb and resource ("Lists the people and bots in the Notion workspace") and adds the secondary read-one mode in the same sentence. The dual list/get behavior is explicit, and nothing else in the sibling list (notion_search, notion_get_page) targets workspace users, so an agent can distinguish it without opening the schema.

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?

Gives concrete conditions for each mode: user_id absent lists the workspace, user_id set to "me" returns the connection's own bot user. It does not name an alternative tool or state when-not to use it (e.g. for looking up page authors via notion_search), so it falls short of full routing guidance.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources