Notion changed its API changelog
API changeloghttps://developers.notion.com/page/changelog
ChangeAPI changelog
Notion MCP notion-update-page command behavior changed: atomic batched updates now require all replacements to succeed or none apply; previously partial success was possible. Empty old_str values now fail validation instead of being silently ignored.
August 20, 2026
NOTION AGENT APIS IN PUBLIC BETA
August 25, 2026
ATOMIC BATCHED CONTENT UPDATES IN NOTION MCP
notion-update-page calls that use the update_content command now apply every content-changing replacement in the batch or none of them. Previously, when one old_str matched no page content and another one in the same call did, the matching replacements were saved and the call returned success — so a batch that removed content in one operation and reinserted it in another could drop that content. These calls now return a validation_error naming the old_str that wasn't found, and the page is left unchanged. Operations whose old_str and new_str are identical are ignored without checking for a match. See Supported tools for the tool's matching rules.old_str must also be a non-empty string. Empty values were previously ignored, which silently skipped the replacement; they now fail validation on both notion-update-page and Update a page's content as markdown.
August 20, 2026
NOTION AGENT APIS IN PUBLIC BETA
Confidence95%
Full diff
=================================================================== --- before +++ after @@ -5,8 +5,14 @@ > Use this file to discover all available pages before exploring further. Skip to main content +August 25, 2026 + +ATOMIC BATCHED CONTENT UPDATES IN NOTION MCP + +notion-update-page calls that use the update_content command now apply every content-changing replacement in the batch or none of them. Previously, when one old_str matched no page content and another one in the same call did, the matching replacements were saved and the call returned success — so a batch that removed content in one operation and reinserted it in another could drop that content. These calls now return a validation_error naming the old_str that wasn’t found, and the page is left unchanged. Operations whose old_str and new_str are identical are ignored without checking for a match. See Supported tools for the tool’s matching rules.old_str must also be a non-empty string. Empty values were previously ignored, which silently skipped the replacement; they now fail validation on both notion-update-page and Update a page’s content as markdown. + August 20, 2026 NOTION AGENT APIS IN PUBLIC BETA
Get the next one in your inbox.
Follow the vendor for free, or write your own prompt and watch any page the same way.