Skip to main content
Glama

notion_retrieve_page_property

Retrieve a specific property from a Notion page, especially for properties with over 25 references. Supports pagination to manage large data sets efficiently.

Instructions

Retrieves a specific property of a Notion page. Use for properties with more than 25 references.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesThe ID of the page
page_sizeNoNumber of items to return (max 100)
property_idYesThe ID of the property to retrieve
start_cursorNoCursor for pagination

Implementation Reference

  • The handler function that implements the core logic of the 'notion_retrieve_page_property' tool by calling NotionClient.retrievePageProperty and formatting the response or error.
    export async function handleRetrievePagePropertyTool(client: NotionClient, args: any) {
        try {
            const propertyArgs: RetrievePagePropertyArgs = {
                page_id: args.page_id,
                property_id: args.property_id,
                ...(args.page_size && { page_size: args.page_size }),
                ...(args.start_cursor && { start_cursor: args.start_cursor })
            };
    
            const response = await client.retrievePageProperty(propertyArgs);
            
            return {
                content: [
                    {
                        type: 'text',
                        text: `Retrieved property: ${args.property_id}\n` +
                              `Type: ${response.type}\n` +
                              `Has more: ${'has_more' in response ? response.has_more : false}\n` +
                              `Next cursor: ${'next_cursor' in response ? response.next_cursor || 'N/A' : 'N/A'}\n` +
                              `Data: ${JSON.stringify(response, null, 2)}`
                    }
                ]
            };
        } catch (error: any) {
            return {
                content: [
                    {
                        type: 'text',
                        text: `Error retrieving page property: ${error.message || 'Unknown error'}`
                    }
                ],
                isError: true
            };
        }
    }
  • The tool definition object containing the name, description, and input schema (JSON Schema) for validating tool inputs.
    export const retrievePagePropertyToolDefinition: Tool = {
        name: 'notion_retrieve_page_property',
        description: 'Retrieves a specific property of a Notion page. Use for properties with more than 25 references.',
        inputSchema: {
            type: 'object',
            properties: {
                page_id: {
                    type: 'string',
                    description: 'The ID of the page'
                },
                property_id: {
                    type: 'string',
                    description: 'The ID of the property to retrieve'
                },
                page_size: {
                    type: 'number',
                    description: 'Number of items to return (max 100)',
                    minimum: 1,
                    maximum: 100
                },
                start_cursor: {
                    type: 'string',
                    description: 'Cursor for pagination'
                }
            },
            required: ['page_id', 'property_id']
        }
    };
  • src/server.ts:43-50 (registration)
    Registration of the tool definition in the MCP server's ListTools handler, making it discoverable.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
        tools: [
            createPageToolDefinition,
            retrievePageToolDefinition,
            updatePageToolDefinition,
            retrievePagePropertyToolDefinition
        ],
    }));
  • src/server.ts:65-66 (registration)
    Dispatch/registration of the tool handler in the MCP server's CallTool switch statement for execution.
    case 'notion_retrieve_page_property':
        return handleRetrievePagePropertyTool(this.client, args);
  • src/server.ts:128-129 (registration)
    Similar dispatch in the standalone server creator's CallTool handler.
    case 'notion_retrieve_page_property':
        return handleRetrievePagePropertyTool(client, args);
Behavior2/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 of behavioral disclosure. It mentions a constraint ('properties with more than 25 references'), which adds some context, but fails to cover key aspects like whether this is a read-only operation, potential rate limits, authentication needs, or error handling. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 highly concise with only two sentences, each serving a clear purpose: the first states the tool's function, and the second provides usage guidance. There is no wasted text, and it is front-loaded with the core action, making it efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, no output schema, no annotations), the description is somewhat complete but has notable gaps. It clarifies the purpose and offers basic usage guidance, but without annotations or an output schema, it lacks details on behavioral traits, return values, and broader context, making it adequate but not fully comprehensive.

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?

The input schema has 100% description coverage, clearly documenting all four parameters (page_id, page_size, property_id, start_cursor) with their purposes and constraints. The description doesn't add any additional parameter details beyond what the schema provides, so it meets the baseline score of 3 where the schema does the heavy lifting.

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?

The description clearly states the action ('Retrieves') and resource ('a specific property of a Notion page'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'notion_retrieve_page' (which retrieves the entire page rather than a specific property), so it doesn't reach the highest score for sibling distinction.

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

Usage Guidelines3/5

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

The description provides some usage context by specifying 'Use for properties with more than 25 references,' which implies when to prefer this tool over alternatives. However, it doesn't explicitly mention when not to use it or name specific alternatives (e.g., 'notion_retrieve_page' for properties with fewer references), leaving the guidance somewhat implied rather than comprehensive.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/michaelwaves/notion-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server