Skip to main content
Glama

update-page

Modify existing Notion pages by updating properties, content, or archiving status to keep information current and organized.

Instructions

Update an existing page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesID of the page to update
propertiesYesUpdated page properties
archivedNoWhether to archive the page

Implementation Reference

  • Handler for the 'update-page' tool. Extracts page_id, properties, and optional archived flag from arguments, constructs parameters, calls Notion's pages.update API, and returns the response as JSON text.
    else if (name === "update-page") {
      const { page_id, properties, archived } = args;
      
      const updateParams = {
        page_id,
        properties,
      };
    
      if (archived !== undefined) {
        updateParams.archived = archived;
      }
    
      const response = await notion.pages.update(updateParams);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the 'update-page' tool, specifying required page_id and properties, and optional archived boolean.
    inputSchema: {
      type: "object",
      properties: {
        page_id: {
          type: "string",
          description: "ID of the page to update"
        },
        properties: {
          type: "object",
          description: "Updated page properties"
        },
        archived: {
          type: "boolean",
          description: "Whether to archive the page"
        }
      },
      required: ["page_id", "properties"]
    }
  • server.js:105-126 (registration)
    Registration of the 'update-page' tool in the tools/list response, including name, description, and input schema.
    {
      name: "update-page",
      description: "Update an existing page",
      inputSchema: {
        type: "object",
        properties: {
          page_id: {
            type: "string",
            description: "ID of the page to update"
          },
          properties: {
            type: "object",
            description: "Updated page properties"
          },
          archived: {
            type: "boolean",
            description: "Whether to archive the page"
          }
        },
        required: ["page_id", "properties"]
      }
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.9/5.0
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 'Update an existing page' which implies a mutation operation, but doesn't specify what permissions are required, whether changes are reversible, or what happens to unspecified properties. This leaves significant gaps in understanding the tool's 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 extremely concise at just three words, front-loading the essential information with zero wasted words. Every element ('Update', 'an existing page') earns its place by clearly communicating the core functionality.

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 insufficiently complete. It doesn't explain what 'update' entails operationally, what the response looks like, or potential side effects. Given the complexity of updating a page with properties and archival options, more context is needed.

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 schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter information 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') and target resource ('an existing page'), making the tool's purpose immediately understandable. It distinguishes from sibling tools like 'create-page' by specifying it works on existing pages, though it doesn't differentiate from 'update-block' or 'update-database' which also update 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 like 'update-block' or 'update-database', nor does it mention prerequisites such as needing a valid page_id. It simply states what the tool does without contextual usage information.

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