# Truncation metadata on notion-fetch

By Steven Van · 2026-08-07

The notion-fetch MCP tool response now includes truncated, unknown\_block\_ids, and unknown\_block\_count when a page is large enough that some subtrees could…

[**Notion**](<https://creatorstoolbox.com/tools/notion>) announced [**Truncation metadata on notion-fetch**](<https://developers.notion.com/page/changelog#august-7-2026>) on August 7, 2026.

## What changed

The notion-fetch MCP tool response now includes truncated, unknown\_block\_ids, and unknown\_block\_count when a page is large enough that some subtrees could not be loaded. unknown\_block\_ids lists up to 50 omitted subtree root IDs, and unknown\_block\_count reports the total number of omitted subtree roots. Pass a returned ID back to notion-fetch to retrieve that subtree directly; treat an object\_not\_found error on retry as a signal that the caller does not have access to the subtree.

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

[Read Truncation metadata on notion-fetch on Creators Toolbox](<https://creatorstoolbox.com/blog/notion-truncation-metadata-on-notion-fetch>)

---
Canonical source: https://creatorstoolbox.com/blog/notion-truncation-metadata-on-notion-fetch