# Atomic batched content updates in Notion MCP

By Steven Van · 2026-08-25

notion-update-page calls that use the update\_content command now apply every content-changing replacement in the batch or none of them.

Notion's [Notion](<https://creatorstoolbox.com/tools/notion>) MCP now makes batched content updates atomic. When a [notion-update-page call](<https://developers.notion.com/page/changelog#august-25-2026>) using the update\_content command includes several replacements, they all apply or none do.

Previously, if one old\_str in a batch matched no page content while another one in the same call did, the matching replacements were saved and the call still returned success. That meant a batch that removed content in one operation and reinserted it in another could end up dropping it. Calls with an unmatched old\_str now return a validation\_error naming the string that wasn't found, and the page is left unchanged.

- Operations where old\_str and new\_str are identical are skipped without checking for a match.

- old\_str must now be a non-empty string on both notion-update-page and Update a page's content as markdown; empty values were previously ignored, which silently skipped the replacement.

[![](<https://notion-demo.mintlify.app/images/og-image.png>)](<https://developers.notion.com/page/changelog#august-25-2026>)

![Notion](<https://www.google.com/s2/favicons?domain=notion.so&sz=128>)

Notion

All-in-one workspace for notes, docs, projects, and wikis — with AI built in for writing, summarizing, and organizing.

[View Notion →](<https://creatorstoolbox.com/tools/notion>)

Sources

[Original source](<https://developers.notion.com/page/changelog#august-25-2026>)

[Read Atomic batched content updates in Notion MCP on Creators Toolbox](<https://creatorstoolbox.com/blog/notion-atomic-batched-content-updates-in-notion-mcp>)

---
Canonical source: https://creatorstoolbox.com/blog/notion-atomic-batched-content-updates-in-notion-mcp