Skip to main content
Glama

mcp-notion__notion-list-favorite-pages

Read-onlyIdempotent

List the current user's favorite pages and databases in sidebar order. Use this when the user refers to a favorite or pinned workspace item. 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-favorite-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

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description's "its server marks it read-only, so it runs straight away" restates that rather than adding new information, and the pagination sentence is the one genuinely additive behavioral note. Nothing is said about result size defaults or what the entries contain.

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?

Three short sentences, with the resource and ordering front-loaded and the usage trigger second, which is the right order. The closing Royally sentence is largely redundant with the read-only annotation and spends space without adding guidance.

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 list tool with full schema coverage and no output schema, the definition covers purpose, trigger, ordering, and pagination, which is most of what an agent needs. Remaining gaps (default page size, shape of returned entries) are minor given that annotations carry the safety profile.

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 itself. The description only reinforces the cursor parameter by advising to follow pagination; it adds nothing about limit bounds or the tracking-only nature of skill, so the baseline of 3 applies.

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?

"List the current user's favorite pages and databases in sidebar order" gives a specific verb, a specific resource (favorites, not all pages), and the ordering. That scope naturally separates it from siblings like notion-list-private-pages, list-recent-pages, and list-shared-pages, though none are named outright.

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?

"Use this when the user refers to a favorite or pinned workspace item" supplies a concrete trigger condition, which is better than most list tools. It stops short of stating exclusions (e.g. use list-recent-pages when the item was merely viewed recently), so the agent still has to infer the negative case.

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