Add content blocks to any Notion page or block. Supports markdown for formatting, letting you extend pages with notes, updates, and more.
Add new content blocks to a page or block. Use when user wants to add content to an existing page.
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | Content to add (supports markdown) | |
| parent_id | Yes | Page or block ID to append to |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral disclosure burden. It only states that blocks are added, without mentioning side effects, permission requirements, error behavior, or whether existing content is preserved. For a write operation, this is inadequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler. The action is front-loaded and the usage clause is immediately helpful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter append operation, the description provides sufficient selection context. It lacks details on return values or edge cases, but the tool is low-complexity and no output schema exists to explain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so both parent_id and content are already documented. The description adds no additional parameter meaning beyond restating that content is added to a page or block.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource ('Add new content blocks to a page or block') and clarifies the target is an existing page, which distinguishes it from create_page. It does not explicitly name alternatives like update_block, but 'new content blocks' conveys that this tool creates rather than modifies blocks.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states when to use the tool: when the user wants to add content to an existing page. It does not provide exclusions or name sibling alternatives, but the primary context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.