Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

update_page

Modify properties of a Notion page by specifying the page ID and updated property values to manage content within the Multi-MCPs server.

Instructions

Update a Notion page properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYes
propertiesYes

Implementation Reference

  • The handler function for the 'update_page' tool. It checks for the Notion token configuration, extracts and validates the page_id from args, and delegates to the Notion client's updatePage method with the provided properties.
    async update_page(args: Record<string, unknown>) {
      if (!cfg.notionToken) throw new Error("NOTION_TOKEN is not configured");
      const pageId = String(args.page_id || "");
      if (!pageId) throw new Error("page_id is required");
      return client.updatePage(pageId, args.properties);
    },
  • The input schema definition for the 'update_page' tool, specifying required 'page_id' (string) and 'properties' (object). Used for validation during tool invocation.
    inputSchema: {
      type: "object",
      properties: {
        page_id: { type: "string" },
        properties: { type: "object" },
      },
      required: ["page_id", "properties"],
    },
  • The tool registration entry for 'update_page' within the registerNotion() function's tools array. Includes name, description, and input schema.
    {
      name: "update_page",
      description: "Update a Notion page properties",
      inputSchema: {
        type: "object",
        properties: {
          page_id: { type: "string" },
          properties: { type: "object" },
        },
        required: ["page_id", "properties"],
      },
    },
  • The NotionClient helper method that performs the actual API request to update a page's properties via Notion's PATCH /v1/pages/{pageId} endpoint. Called by the tool handler.
    updatePage(pageId: string, properties: unknown) {
      return this.request(`/v1/pages/${pageId}`, {
        method: "PATCH",
        body: { 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 implies a mutation operation ('Update') but doesn't specify permissions required, whether changes are reversible, rate limits, or what the response looks like. This leaves significant gaps in understanding the tool's behavior and safety profile.

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 no wasted words, making it easy to parse. It front-loads the core action and resource, though it could benefit from additional context without sacrificing brevity.

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 no annotations, 0% schema coverage, no output schema, and nested objects in parameters, the description is inadequate. It lacks details on behavior, parameter usage, error handling, and output, leaving the agent with insufficient information to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description must compensate. It mentions 'page_id' and 'properties' implicitly but doesn't explain what 'properties' entails (e.g., key-value pairs for Notion page fields) or provide examples. This adds minimal semantic value beyond the bare parameter names.

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 verb 'Update' and the resource 'a Notion page properties', making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'update_card', which might be conceptually similar but for a different resource type, leaving room for slight ambiguity in sibling differentiation.

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 'create_page' or 'update_card', nor does it mention prerequisites such as needing an existing page ID. It only states what the tool does, without context for usage decisions.

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/TaylorChen/muti-mcps'

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