Better Notion MCP

pages

Create, retrieve, update, move, archive, duplicate, or restore individual Notion documents and database rows, including markdown content and property values.

Instructions

Page CRUD for individual pages and database rows.

Actions (required params -> optional):

create (parent_id -> title, content, properties, icon, cover)
get (page_id -> content_limit, content_cursor): returns markdown content; bounded reads return content_truncated and next_cursor
get_property (page_id, property_id)
update (page_id -> title, content, append_content, properties, icon, cover, archived)
move (page_id, parent_id)
archive (page_id) / restore (page_id)
duplicate (page_id -> parent_id)

Use databases instead for querying or bulk row operations. Property format: simple values auto-convert -- string for title/rich_text/select/status, number for number, boolean for checkbox, string[] for multi_select, ISO date "2025-01-15" for date. Example: properties: {"Name": "My Page", "Status": "In Progress", "Tags": ["urgent", "work"]}

Input Schema

TableJSON Schema

Name	Required	Description
`icon`	No	Icon: emoji (e.g. "(icon)"), external URL (https://...), or built-in shorthand (name:color, e.g. "document:gray")
`cover`	No	Cover image: URL or built-in shorthand (gradient_1..11, solid_red/yellow/blue/beige, nasa_, met_, rijksmuseum_, woodcuts_)
`title`	No	Page title
`action`	Yes	Action to perform
`content`	No	Markdown content
`page_id`	No	Page ID (required for most actions)
`archived`	No	Archive status
`page_ids`	No	Multiple page IDs for batch operations
`parent_id`	No	Parent page or database ID
`properties`	No	Page properties (for database pages). Use simple values -- auto-converted to Notion format. String: title/rich_text/select/status. Number: number. Boolean: checkbox. String[]: multi_select. ISO date string: date. Object with Notion structure: pass through as-is.
`property_id`	No	Property ID (for get_property action)
`content_limit`	No	Max page blocks to return for get; use next_cursor to continue
`append_content`	No	Markdown to append
`content_cursor`	No	Cursor from a previous bounded pages get

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.41.4Sep 12, 2026

addedInput schema / properties / content_cursor

Added value: +{
+  "description": "Cursor from a previous bounded pages get",
+  "type": "string"
+}

addedInput schema / properties / content_limit

Added value: +{
+  "description": "Max page blocks to return for get; use next_cursor to continue",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "number"
+}

Changed1 schema field changedv2.37.0Jul 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

Changed3 schema fields changedv2.30.4May 1, 2026

changedInput schema / properties / icon / description

Previous value: -"Icon: emoji (e.g. \"📋\"), external URL (https://...), or built-in shorthand (name:color, e.g. \"document:gray\")"New value: +"Icon: emoji (e.g. \"(icon)\"), external URL (https://...), or built-in shorthand (name:color, e.g. \"document:gray\")"

removedInput schema / properties / prepend_content

Removed value: -{
-  "description": "[Deprecated] Not supported by Notion API — use blocks tool to insert at specific position",
-  "type": "string"
-}

changedInput schema / properties / properties / description

Previous value: -"Page properties (for database pages)"New value: +"Page properties (for database pages). Use simple values -- auto-converted to Notion format. String: title/rich_text/select/status. Number: number. Boolean: checkbox. String[]: multi_select. ISO date string: date. Object with Notion structure: pass through as-is."

Changed5 schema fields changedv2.18.0Mar 12, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "create",
-  "get",
-  "update",
-  "archive",
-  "restore",
-  "duplicate"
-]New value: +[
+  "create",
+  "get",
+  "get_property",
+  "update",
+  "move",
+  "archive",
+  "restore",
+  "duplicate"
+]

changedInput schema / properties / cover / description

Previous value: -"Cover image URL"New value: +"Cover image: URL or built-in shorthand (gradient_1..11, solid_red/yellow/blue/beige, nasa_*, met_*, rijksmuseum_*, woodcuts_*)"

changedInput schema / properties / icon / description

Previous value: -"Emoji icon"New value: +"Icon: emoji (e.g. \"📋\"), external URL (https://...), or built-in shorthand (name:color, e.g. \"document:gray\")"

changedInput schema / properties / prepend_content / description

Previous value: -"Markdown to prepend"New value: +"[Deprecated] Not supported by Notion API — use blocks tool to insert at specific position"

addedInput schema / properties / property_id

Added value: +{
+  "description": "Property ID (for get_property action)",
+  "type": "string"
+}

First observedDec 28, 2025

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint false, destructiveHint false), so the description adds useful context about get returning markdown, bounded reads returning content_truncated/next_cursor, update supporting append_content, and archive/restore semantics. It does not mention auth requirements or rate limits, but for a CRUD tool the added behavioral detail is substantial.

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 front-loaded with the tool's purpose, then uses a compact action list with required-to-optional parameter mappings. The property-format example is concise and earns its place by preventing format errors.

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

Completeness5/5

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

An output schema exists, so the description need not explain return values in full, and it still notes truncation/cursor behavior for bounded reads. The action list matches the enum exactly, and the alternative-tool guidance plus property format covers the key invocation details for a 14-parameter tool.

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

Parameters5/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 each parameter. The description goes beyond the schema by mapping which parameters are required or optional per action, and by giving a concrete property auto-conversion example that clarifies expected value shapes.

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

Purpose5/5

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

The description states a specific verb+resource: 'Page CRUD for individual pages and database rows,' and enumerates all supported actions. It distinguishes the tool from the sibling 'databases' tool by directing querying and bulk row operations there.

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

Usage Guidelines4/5

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

It explicitly names the alternative 'databases' for querying or bulk row operations, which gives clear routing guidance. However, it does not address other sibling tools like 'blocks' or 'comments' that an agent might consider for related content operations.

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

Deploy Server