Skip to main content
Glama

mcp-notion__notion-list-shared-pages

Read-onlyIdempotent

List pages and databases in the current user's Shared sidebar section. Use this to browse content shared directly with the user. 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-shared-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.1/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, and the line 'its server marks it read-only, so it runs straight away' largely restates that rather than extending it. The one genuinely additive behavior detail is the instruction to follow cursor pagination for complete lists; ordering, result shape and scope caveats (e.g. whether shared-with-user content the user has hidden appears) are not covered.

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 scope, then alternatives, then pagination – a sensible order with little waste. The 'Through Royally: its server marks it read-only, so it runs straight away' clause is deployment chatter that repeats the annotations and could be dropped.

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 read-only, fully annotated list tool with a 100%-documented schema and no output schema, the description covers scope, alternatives and pagination adequately. It stops short of describing what a result entry contains or default page size, which would help an agent plan a browse loop.

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?

Schema description coverage is 100%, so limit, cursor, skill, site_id and instructions_version are all documented in the schema; the baseline applies. The description only reinforces the cursor parameter via the pagination sentence and adds nothing about limit bounds or the tracking-only nature of skill.

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 ('List pages and databases') plus a precise scope ('the current user's Shared sidebar section'), which separates it from the sibling list tools for favorites, private pages and recent pages without naming them.

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 explicit when-to-use ('browse content shared directly with the user') and routes to named alternatives for other intents: search for keyword/title lookups, connector_search for connected sources. Nothing is left to 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