Skip to main content
Glama
Sign In
awkoy

notion-mcp-server

by awkoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Notion Write

notion_write
Destructive

Executes one named Notion write operation—create, update, archive, or comment—with single or batch payloads and schema-guided error recovery.

Instructions

Run one Notion write operation by name. Archive, trash and delete operations remove content — confirm with the user before running them.

Two ways to call: • Single: { operation: "set_page_title", payload: { page_id, title } } • Batch: { operation: "set_page_title", payload: { items: [{page_id, title}, ...], atomic?: false, idempotency_key?: "...", concurrency?: 3 } } create_page, append_blocks, update_block and update_page_markdown also take a markdown string.

Responses are slimmed; pass verbose:true inside payload (single) or per item (batch) for the raw Notion object. Every id field (page_id, block_id, database_id, view_id, …) also accepts a Notion URL, as copied from Share → Copy link.

If the payload is malformed, the error response includes the schema + a working example so you can correct and retry in one round-trip. Call notion_describe(operation) ahead of time only for complex shapes (block trees, database property definitions, batch_mixed_blocks).

Input Schema

NameRequiredDescriptionDefault
payloadYesOperation parameters. Pass either single-op fields directly, or { items: [...], atomic?, idempotency_key?, concurrency? } for batch.
operationYesThe write operation to run. This list is the complete menu of write operations enabled on this server; notion_describe(operation) returns any operation's full schema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.3.0
    • changedInput schema / properties / operation / enum
      Previous value: -[
-  "create_database",
-  "update_database",
-  "delete_database",
-  "update_data_source",
-  "delete_data_source",
-  "create_view",
-  "update_view",
-  "delete_view",
-  "add_page_comment",
-  "add_discussion_comment",
-  "update_comment",
-  "delete_comment",
-  "upload_file",
-  "create_page",
-  "set_page_title",
-  "set_page_property",
-  "set_page_properties",
-  "archive_page",
-  "trash_page",
-  "restore_page",
-  "move_page",
-  "update_page_markdown",
-  "append_blocks",
-  "update_block",
-  "delete_block",
-  "batch_mixed_blocks"
-]New value: +[
+  "create_database",
+  "update_database",
+  "delete_database",
+  "create_view",
+  "update_view",
+  "delete_view",
+  "add_page_comment",
+  "add_discussion_comment",
+  "update_comment",
+  "delete_comment",
+  "upload_file",
+  "update_data_source",
+  "delete_data_source",
+  "create_page",
+  "set_page_title",
+  "set_page_property",
+  "set_page_properties",
+  "archive_page",
+  "trash_page",
+  "restore_page",
+  "move_page",
+  "update_page_markdown",
+  "append_blocks",
+  "update_block",
+  "delete_block",
+  "batch_mixed_blocks"
+]
  2. Addedv3.0.1

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare destructive and open-world behavior, but the description adds specific operational context: archive/trash/delete remove content, responses are slimmed unless verbose is requested, malformed payloads return schema plus a working example, and ID fields accept Notion URLs. These details materially improve safe invocation beyond what the annotations provide.

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 core action and the destructive warning, then moves into invocation patterns, response behavior, error recovery, and schema lookup guidance. For a 26-operation dispatcher, every section earns its place and there is no filler.

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 tool's complexity, lack of output schema, nested payload, and destructive annotations, the description covers the important gaps: batch vs single invocation, destructive confirmation, verbose responses, URL-accepting IDs, and error recovery via schema. An agent has enough information to invoke it correctly without opening separate documentation.

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?

Although the schema covers operation and payload at 100%, the payload schema is intentionally generic with additionalProperties, so the description supplies essential semantics: direct single-op fields, batch items with atomic/idempotency_key/concurrency, markdown arguments for selected operations, and verbose placement. It adds substantial meaning beyond the schema's generic shape.

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 opens with a specific verb and resource: 'Run one Notion write operation by name.' It distinguishes this from read and describe siblings by framing it as writes and by pointing to notion_describe only for complex operation shapes.

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?

It gives concrete calling patterns for single vs batch payloads, explicitly warns to confirm archive/trash/delete operations with the user, and routes agents to notion_describe only for complex shapes such as block trees and database property definitions. This is unusually clear about when to use the tool and when to consult the sibling instead.

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

Deploy Server

Other Tools