Skip to main content
Glama

Append Simple Content

notion_append_content

Append common Notion content types like paragraphs, headings, lists, and more to any page without writing raw block JSON. Simplifies page editing by converting simplified items into valid Notion blocks.

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.
Behavior3/5

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

Annotations already declare safety profile (not readonly, not destructive, not idempotent). Description adds minor context about server conversion but doesn't elaborate on behavior beyond what's implied by the action.

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, front-loaded with purpose, no filler. Efficient use of words.

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 tool complexity (4 params, nested objects, no output schema), the description covers purpose, usage, and alternatives. Could elaborate on defaults for code language or to-do checked, but schema handles details.

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%, so description adds little beyond schema. The hint 'Keep batches reasonably small' provides marginal extra guidance.

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 without raw JSON, lists supported types, and explicitly distinguishes from notion_append_block_children for unsupported types.

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?

Provides explicit when-to-use ('everyday page editing') and when-not-to-use ('unsupported block types or advanced rich text'), with a direct alternative: notion_append_block_children.

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/suekou/mcp-notion-server'

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