Skip to main content
Glama

notion_update_page_properties

Modify properties of Notion pages or database items to update columns and fields with new values.

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 the tool: sends PATCH request to Notion API /pages/{page_id} to update the 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();
    }
  • Server-side dispatch handler for the tool call, validates arguments and delegates to NotionClientWrapper.
    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;
    }
  • MCP tool schema definition including name, description, and input validation schema.
    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"],
      },
    };
  • Registration of the tool in the ListToolsRequest handler by including its schema in the allTools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      const allTools = [
        schemas.appendBlockChildrenTool,
        schemas.retrieveBlockTool,
        schemas.retrieveBlockChildrenTool,
        schemas.deleteBlockTool,
        schemas.updateBlockTool,
        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),
      };
    });
  • TypeScript type definition for the tool arguments used in the server handler.
    export interface UpdatePagePropertiesArgs {
      page_id: string;
      properties: Record<string, any>;
      format?: "json" | "markdown";
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation but doesn't mention permission requirements, whether changes are reversible, rate limits, or what happens to existing properties not included in the update. This leaves significant gaps for a mutation tool.

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 appropriately sized and front-loaded with the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the update operation returns, error conditions, or behavioral constraints. The 100% schema coverage helps with parameters, but overall context for safe and effective use is lacking.

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 already documents all three parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema, maintaining the baseline score 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 properties') and target ('page or an item in a Notion database'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like notion_update_block or notion_update_database, which also perform updates on different Notion resources.

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. It doesn't mention sibling tools like notion_update_block (for block content) or notion_update_database (for database schema), nor does it specify prerequisites or typical use cases beyond the basic action.

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

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