Skip to main content
Glama
SunCreation

MCP Notion Server (@suncreation)

by SunCreation

notion_update_page_properties

Modify properties of Notion pages or database items by specifying page ID and property updates to change fields like status, dates, or tags.

Instructions

Update properties of a page or an item in a Notion database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesThe ID of the page or database item to update.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
propertiesYesProperties to update. These correspond to the columns or fields in the database.
formatNoSpecify the response format. 'json' returns the original data structure, 'markdown' returns a more readable format. Use 'markdown' when the user only needs to read the page and isn't planning to write or modify it. Use 'json' when the user needs to read the page with the intention of writing to or modifying it.markdown

Implementation Reference

  • Core implementation of updatePageProperties method that makes a PATCH request to the Notion API to update page properties
    async updatePageProperties(
      page_id: string,
      properties: Record<string, any>
    ): Promise<PageResponse> {
      const body = { properties };
    
      const response = await fetch(`${this.baseUrl}/pages/${page_id}`, {
        method: "PATCH",
        headers: this.headers,
        body: JSON.stringify(body),
      });
    
      return response.json();
    }
  • Tool request handler that validates arguments and calls the updatePageProperties method on the Notion client
    case "notion_update_page_properties": {
      const args = request.params
        .arguments as unknown as args.UpdatePagePropertiesArgs;
      if (!args.page_id || !args.properties) {
        throw new Error(
          "Missing required arguments: page_id and properties"
        );
      }
      response = await notionClient.updatePageProperties(
        args.page_id,
        args.properties
      );
      break;
  • Tool schema definition with name, description, inputSchema (page_id and properties as required fields)
    export const updatePagePropertiesTool: Tool = {
      name: "notion_update_page_properties",
      description: "Update properties of a page or an item in a Notion database",
      inputSchema: {
        type: "object",
        properties: {
          page_id: {
            type: "string",
            description:
              "The ID of the page or database item to update." +
              commonIdDescription,
          },
          properties: {
            type: "object",
            description:
              "Properties to update. These correspond to the columns or fields in the database.",
          },
          format: formatParameter,
        },
        required: ["page_id", "properties"],
      },
    };
  • TypeScript interface definition for UpdatePagePropertiesArgs including page_id, properties, and optional format
    export interface UpdatePagePropertiesArgs {
      page_id: string;
      properties: Record<string, any>;
      format?: "json" | "markdown";
    }
  • Tool registration in ListToolsRequestSchema handler where updatePagePropertiesTool is included in the allTools array
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      const allTools = [
        schemas.appendBlockChildrenTool,
        schemas.retrieveBlockTool,
        schemas.retrieveBlockChildrenTool,
        schemas.deleteBlockTool,
        schemas.updateBlockTool,
        schemas.createPageTool,
        schemas.retrievePageTool,
        schemas.updatePagePropertiesTool,
        schemas.listAllUsersTool,
        schemas.retrieveUserTool,
        schemas.retrieveBotUserTool,
        schemas.createDatabaseTool,
        schemas.queryDatabaseTool,
        schemas.retrieveDatabaseTool,
        schemas.updateDatabaseTool,
        schemas.createDatabaseItemTool,
        schemas.createCommentTool,
        schemas.retrieveCommentsTool,
        schemas.searchTool,
      ];
      return {
        tools: filterTools(allTools, enabledToolsSet),
      };
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool updates properties, implying a mutation, but fails to mention critical aspects like required permissions, whether changes are reversible, rate limits, or what the response looks like (since there's no output schema). This leaves significant gaps in understanding the tool's behavior and risks.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to grasp quickly. Every part of the sentence contributes to understanding, with zero waste or redundancy.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a mutation tool with 3 parameters, no annotations, and no output schema, the description is insufficient. It doesn't cover behavioral risks, response format, or usage context, leaving the agent with incomplete information to safely and effectively invoke the tool. More detail is needed to compensate for the lack of structured data.

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 the schema fully documents all parameters. The description adds no additional meaning beyond what's in the schema, such as examples of property formats or constraints. It merely restates the purpose without enhancing parameter understanding, meeting the baseline for high schema coverage.

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 ('Update') and resource ('properties of a page or an item in a Notion database'), making the purpose evident. However, it doesn't explicitly differentiate from siblings like 'notion_update_block' or 'notion_update_database', which also perform updates on different resources, leaving some ambiguity about when to choose this specific tool.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as 'notion_update_block' for block-level changes or 'notion_update_database' for database-level updates. It lacks context on prerequisites, like needing a page ID, and doesn't mention any exclusions or specific scenarios where this tool is preferred over others.

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

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/SunCreation/mcp-notion-server'

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