Skip to main content
Glama
SadaaYogee

Notion MCP Server

by SadaaYogee

Append Simple Content

notion_append_content

Append paragraphs, headings, lists, to-dos, quotes, callouts, code blocks, or dividers to a Notion page using simplified content items, removing the need to write raw Notion block JSON.

Instructions

Append common Notion content without writing raw Notion block JSON. Use this for everyday page editing when the user wants to add paragraphs, headings, lists, todos, quotes, callouts, code blocks, or dividers. For unsupported block types or advanced rich text annotations, use notion_append_block_children with raw Notion block objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesSimplified content items to append in order. Keep batches reasonably small for easier review.
formatNoSpecify the response format. 'json' returns the original data structure, 'markdown' returns a more readable format. Use 'markdown' when the user only needs to read the page and isn't planning to write or modify it. Use 'json' when the user needs to read the page with the intention of writing to or modifying it.
block_idYesThe parent block or page ID to append content to.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
positionNoWhere to insert the content. Omit this to append at the end.
Behavior4/5

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

Annotations already indicate the tool is not read-only, not idempotent, and not destructive. The description adds that it appends content, which is consistent. It does not add extra behavioral details, but given the annotations, this is sufficient.

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 concise with two sentences, no unnecessary words, and front-loads the key purpose. Every sentence earns its place.

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

Completeness4/5

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

Given the tool has 4 parameters, no output schema, and annotations cover safety, the description is complete enough. It explains when to use and the main functionality. Minor gap: no mention of return value, but that's acceptable without output schema.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all parameters, so the baseline is 3. The description does not add additional parameter-level details beyond the schema, but it provides context for the simplified content types.

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 clearly states the tool appends common Notion content using simplified types, avoiding raw JSON. It lists supported block types and explicitly distinguishes itself from notion_append_block_children, providing a specific verb and resource.

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 explicitly says when to use (everyday page editing with common blocks) and when not to (unsupported block types or advanced rich text), and names the alternative tool (notion_append_block_children). This provides clear context for tool selection.

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/SadaaYogee/MCP-Notion-Server'

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