Retrieve a specific property from a Notion page by page ID and property ID, with pagination for large results.
Get page property by ID
| Name | Required | Description | Default |
|---|---|---|---|
| page_id | Yes | Page ID containing the property | |
| page_size | No | Number of results per page (max 100) | |
| property_id | Yes | Property ID to fetch | |
| start_cursor | No | Pagination cursor |
Changes observed during successful MCP inspections.
v1.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It implies read-only via 'Get' but does not describe permissions, rate limits, or pagination behavior, even though pagination parameters exist in the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with zero waste. It is arguably under-specified for the tool's complexity, but the dimension rewards conciseness rather than completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description should clarify what is returned and how the pagination parameters affect the response. It does not, leaving significant ambiguity for a four-parameter tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so all parameters are documented in the schema itself. The description adds only 'by ID', which is redundant with the required parameters, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb 'Get' and resource 'page property', implicitly distinguishing it from sibling notion_get_page. However, it offers no explicit sibling differentiation or scope clarification beyond the name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance or alternatives are provided. 'By ID' implies a precondition but does not explain when to choose this tool over notion_get_page or notion_query_database.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.