Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

create_page

Create a Notion page within a specified parent page or database, enabling content organization and management through the Multi-MCPs server.

Instructions

Create a Notion page under a parent page or database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_idYes
propertiesYes

Implementation Reference

  • Handler function for the create_page tool that validates inputs and calls the Notion client's createPage method.
    async create_page(args: Record<string, unknown>) {
      if (!cfg.notionToken) throw new Error("NOTION_TOKEN is not configured");
      const parentId = String(args.parent_id || "");
      if (!parentId) throw new Error("parent_id is required");
      return client.createPage(parentId, args.properties);
    },
  • Input schema defining parent_id and properties for create_page tool.
    inputSchema: {
      type: "object",
      properties: {
        parent_id: { type: "string" },
        properties: { type: "object" },
      },
      required: ["parent_id", "properties"],
    },
  • Tool registration entry for create_page including name, description, and schema.
    {
      name: "create_page",
      description: "Create a Notion page under a parent page or database",
      inputSchema: {
        type: "object",
        properties: {
          parent_id: { type: "string" },
          properties: { type: "object" },
        },
        required: ["parent_id", "properties"],
      },
    },
  • Helper method in NotionClient class that creates a Notion page via API request.
    createPage(parentId: string, properties: unknown) {
      return this.request(`/v1/pages`, {
        method: "POST",
        body: { parent: { page_id: parentId, database_id: undefined }, 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 the tool creates a page but doesn't mention permissions required, whether the operation is idempotent, rate limits, or what happens on failure. It lacks details on the response format or any side effects, leaving 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 front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action, resource, and context concisely.

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 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on parameter semantics, behavioral traits (e.g., permissions, errors), and expected outputs, making it inadequate for safe and effective use by an AI agent.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'parent page or database' (hinting at 'parent_id') and implies 'properties' for page content, but doesn't explain what 'properties' should contain (e.g., Notion property types like title, rich text) or format requirements. This adds minimal value beyond the bare schema.

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 ('Create') and resource ('a Notion page'), and specifies the location ('under a parent page or database'). It distinguishes from siblings like 'search_pages' or 'update_page' by focusing on creation. However, it doesn't explicitly differentiate from 'create_card' or 'create_issue' in terms of platform context.

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 prerequisites (e.g., needing a parent page/database ID), exclusions, or comparisons to siblings like 'update_page' or 'query_database'. Usage is implied but not explicitly stated.

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