Skip to main content
Glama
n24q02m

Better Notion MCP

by n24q02m
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

pages

Manage Notion pages and database rows with actions for create, read, update, move, archive, and duplicate. Supports markdown content and properties.

Instructions

Page CRUD for individual pages and database rows.

Actions (required params -> optional):

  • create (parent_id -> title, content, properties, icon, cover)

  • get (page_id): returns markdown content

  • 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": ["tag1", "tag2"], "Due": "2025-06-01", "Count": 42, "Done": true}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNoIcon: emoji (e.g. "(icon)"), external URL (https://...), or built-in shorthand (name:color, e.g. "document:gray")
coverNoCover image: URL or built-in shorthand (gradient_1..11, solid_red/yellow/blue/beige, nasa_*, met_*, rijksmuseum_*, woodcuts_*)
titleNoPage title
actionYesAction to perform
contentNoMarkdown content
page_idNoPage ID (required for most actions)
archivedNoArchive status
page_idsNoMultiple page IDs for batch operations
parent_idNoParent page or database ID
propertiesNoPage 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_idNoProperty ID (for get_property action)
append_contentNoMarkdown to append

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations show readOnlyHint=false, which is consistent with mutation actions described. The description adds behavioral details such as property auto-conversion, markdown content handling, and return behavior for 'get' action. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with a clear purpose statement. It is somewhat lengthy due to detailed action list and property examples, but every sentence adds value and is not redundant.

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?

Given the complexity (12 parameters, nested objects, output schema exists), the description covers all major functionalities, provides usage guidance, property formatting, and alternatives. It is complete for agent decision-making.

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 coverage is 100%, but the description adds significant value beyond the schema by listing actions with parameter requirements, explaining property format conversion with examples, and providing context for icon and cover formats.

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 'Page CRUD for individual pages and database rows' and lists specific actions with clear purpose. It distinguishes from sibling 'databases' by explicitly stating to use that tool for querying or bulk operations.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance by listing actions with required/optional parameters and a clear alternative: 'Use `databases` instead for querying or bulk row operations.' It also includes property format examples.

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/n24q02m/better-notion-mcp'

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