Notion Release Notes

More filters in Notion MCP view tools

The notion-create-view and notion-update-view tools now apply relation, person, status, created by, last edited by, unique ID, last visited, verification, and place filters. Previously, some calls succeeded but saved a view without the requested filter.

Use a page URL or ID for relation filters and a user ID or "me" for person filters. Invalid values now return an error. See Supported tools for accepted values, and read the notion://docs/view-dsl-spec resource for the full configuration syntax.

Verification filters now round-trip through view responses for both matching (status) and non-matching (does_not_equal) conditions. Data source queries accept the same conditions.

prop() references in formula property writes

Formula expressions submitted through Update a data source now store prop("Property Name") references exactly as written. Previously, the API accepted some expressions but silently rewrote them — most visibly, a reference to a unique ID property dropped the ID’s prefix from computed values, and a prop() reference inside an array literal emptied the array. Expressions the API can’t store now return a validation_error instead. Formulas saved before this fix keep their old stored expression until you resubmit the update.

Formula properties created through the API also now keep their result type, so number formatting options stay available in Notion and other formulas can reference them with prop().

Readable formula expressions in data source schemas

Retrieve a data source is beginning to return formula expressions using the same prop("Property Name") syntax you write. This change is rolling out gradually over the coming days; expressions that can’t be rendered faithfully in this syntax continue to use the internal property reference syntax.

Admin API reference for agents

The Admin API reference now covers the endpoints for managing agents in a workspace: credit usage and limits, permissions, status, creation policy, and workflow metadata.

Filter properties on page writes

Create a page and Update page properties now accept the same filter_properties query parameter as Retrieve a page. Pass the IDs of the properties you want, and the write response includes only those properties. This keeps responses small and fast for pages with many properties.

SDK support: @notionhq/client v5.25.0 adds filter_properties to pages.create() and pages.update().

Truncation metadata on notion-fetch

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.

unsupported formula and rollup property values

The API can now return formula and rollup page property values and property item values with type set to "unsupported" and an empty unsupported object. This happens when a value depends on too many related pages or nested formulas and rollups. The response doesn’t include a partial value. Treat the property as unavailable. Rollups still include the function field. To make the value available, reduce the number of related pages or simplify the nested formulas and rollups.

JavaScript SDK 5.24.0

We released @notionhq/client v5.24.0. It adds client.blocks.meetingNotes.create() for creating a meeting note, typed unsupported formula and rollup values, and APIErrorCode.InvalidBeta for handling invalid_beta responses.

Custom Agents can now run right after an AI Meeting Note is finished. No more need to manually update status trackers, post recaps to the project channel, or file tickets by hand.

Here’s a few of our favorite post-meeting workflows:

• Update your project tracker with the latest status
• Post a recap to Slack or email with decisions and next steps
• Turn feedback into tickets for your engineering team

To get started, open your Custom Agent’s settings, add the Meeting note summarized trigger, and choose which meetings it kicks off. After your next call, your agent will get to work.

Learn more about Custom Agent triggers →

Clearer per-tool access status

The current_tool_access status previously called limited_free_trial is now available_with_limit. The new name makes clear that a tool is available until the usage limit included with the workspace’s plan is reached. This is a naming and description update only; it does not change tool availability or usage limits.

Fetch documentation resources with the fetch tool

The Notion MCP fetch tool now accepts notion://docs/* URIs (for example, notion://docs/enhanced-markdown-spec) and returns the same content as the MCP resource of the same URI. This gives MCP clients that cannot read MCP resources a way to load the specs referenced in tool descriptions.