notion-mcp-server

retrieve-page-property

Retrieve paginated property values for relation and rollup properties with many items.

Instructions

Get a property with pagination (for relation/rollup with many items). For simple properties, use retrieve-page instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_id": "<page_id>",
      "property_id": "<property_id>"
    },
    "name": "retrieve-page-property"
  }
}

Input Schema

Name	Required	Description
`page_id`	Yes	Page ID
`property_id`	Yes	Property ID (from page properties)
`start_cursor`	No	Pagination cursor from previous response
`page_size`	No	Number of results (1-100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.14.0May 27, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses pagination support but does not mention other behavioral traits such as read-only nature, error handling, or rate limits. The description adds some context but is not fully comprehensive for a tool with no annotations.

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 extremely concise with two sentences, each serving a clear purpose: defining the tool's use case and directing to an alternative. No extraneous information, perfectly front-loaded.

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?

Given the tool's moderate complexity (4 parameters) and no output schema, the description is fairly complete. It explains when to use it, but does not describe the return format or pagination cursors in detail. Still, it provides enough context for an agent to correctly select and invoke the tool.

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 coverage is 100%, so the baseline is 3. The description mentions 'pagination' which implies the use of start_cursor and page_size, but does not add significant meaning beyond the schema descriptions. It adequately complements the schema without overdoing it.

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?

The description clearly states the tool retrieves a property with pagination, specifically for relation/rollup with many items. It distinguishes itself from the sibling tool retrieve-page by naming it directly and specifying when to use the alternative.

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?

Explicit usage guidance is provided: use this tool for relation/rollup properties with many items, and for simple properties, use retrieve-page instead. This tells the agent when to choose this tool over its sibling.

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