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"]
      }
    },
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', implying a mutation operation, but doesn't disclose permissions needed, whether changes are reversible, rate limits, or what happens to unmentioned properties. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero waste. It's front-loaded and appropriately sized for the tool's purpose, making it easy to parse quickly.

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 tool's complexity (mutation with 3 parameters, nested objects), no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances, leaving significant gaps for an AI agent to understand how to use it effectively.

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 (page_id, properties, archived). The description adds no additional meaning beyond what the schema provides, such as examples of properties or archiving implications. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update an existing page' clearly states the verb (update) and resource (page), but it's vague about what aspects can be updated and doesn't differentiate from sibling tools like 'update-block' or 'update-database'. It meets the basic requirement but lacks specificity.

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 an existing page ID. It's a generic statement with no contextual usage information.

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/Sjotie/notionMCP'

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