Skip to main content
Glama

mcp-notion__notion-list-private-pages

Read-onlyIdempotent

List the current user's top-level pages and databases in their Private sidebar section. Use this to browse private workspace structure. For content searches, including keywords and titles, use search. Use connector_search, when listed, for connected sources. Follow cursor pagination when the complete list is needed. 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-list-private-pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (1-200).
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.
cursorNoOpaque pagination cursor from the previous response.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully carried by structured data. The description's added value is limited to pagination behavior and a note that the server treats it as read-only, the latter essentially restating the annotation; it says nothing about ordering, result shape, or whether child pages appear.

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 the core purpose, then alternatives, then pagination guidance — a sensible ordering with no padding sentences. The trailing 'Through Royally' sentence is slightly jarring in phrasing but is a single short line and adds execution context.

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 zero-required-parameter read-only list with full schema coverage and no output schema, the description covers scope, alternatives, and pagination adequately. A small residual gap is that it does not state what fields each returned page/database carries or ordering behavior, which an agent might want before rendering results.

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% and every parameter carries its own description, so the baseline is 3. The description earns an extra point by telling the agent to iterate the cursor when a complete list is needed, which explains the practical purpose of the cursor parameter beyond the schema's 'opaque pagination cursor from the previous response'.

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?

Names a specific verb and resource ('List the current user's top-level pages and databases') and scopes it to the 'Private sidebar section', which differentiates it from favorite/recent/shared page lists by data source rather than by naming them. The scope is clear enough that an agent can pick it out, though it never explicitly contrasts with sibling list tools such as notion-list-favorite-pages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit positive case ('browse private workspace structure'), an explicit exclusion with the correct alternative for text/title lookups ('use search'), a further alternative ('connector_search, when listed, for connected sources'), and a procedural cue ('follow cursor pagination when the complete list is needed'). Both when-to-use and when-not-to-use are covered without inference.

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