supabase-notion MCP Server

Create a Notion page

notion_create_page

Creates a new Notion page from markdown, including headings, lists, quotes, and paragraphs, and uses the default parent page when no parent ID is provided.

Instructions

Create a new Notion page from markdown (headings, bullet and numbered lists, quotes, paragraphs). Uses NOTION_PARENT_PAGE_ID when parentId is omitted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "markdown": "<markdown>"
    },
    "name": "notion_create_page"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`markdown`	Yes
`parentId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write/external nature is known. The description adds genuinely useful context by enumerating the supported markdown subset, implicitly warning that other block types will not render. It stops short of disclosing permission requirements, rate limits, or failure behavior for a mutation against an external service.

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?

Two sentences, no filler, with the core action and content format front-loaded and the parent-resolution rule as the follow-up. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say what comes back — most importantly the new page's ID or URL, which the agent needs to chain into notion_get_page. It also omits what happens when neither parentId nor NOTION_PARENT_PAGE_ID is available. Adequate to invoke, incomplete for follow-up work.

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

Parameters4/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, and it does for two of three parameters: markdown is scoped to a specific syntax subset, and parentId's default resolution via NOTION_PARENT_PAGE_ID is explained. The title parameter is left to its schema constraints (minLength 1, maxLength 200) with no added meaning, keeping it short of a 5.

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?

States a specific verb and resource ("Create a new Notion page") and names the content format (markdown), which immediately separates it from the read-oriented siblings notion_search and notion_get_page. It does not explicitly name those siblings, so the differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The fallback rule ("Uses NOTION_PARENT_PAGE_ID when parentId is omitted") gives a concrete condition for omitting a parameter, which is real usage guidance. However, it never says when to prefer this tool over other creation paths, nor states the prerequisite that the Notion integration must have access to the parent page — a common failure mode.

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

Deploy Server