Notion MCP Tools Descriptions Incomplete/Truncated in Cursor, Causing Function Malfunctions

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using Notion MCP in Cursor, the descriptions of Notion MCP tools are either incomplete or truncated, which results in some of their functions failing to work properly. Notably, this issue does not occur on other MCP-compatible clients such as Gemini CLI and Claude — the tool descriptions display fully and all functions operate as expected there.

Steps to Reproduce

directly check the descriptions of the MCP tools or use the sections of Notion syntax that appear later in the tool descriptions

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

This applies to all models.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @shuo_liang

I can’t reproduce this with the Notion MCP server.

User:

Can list the description of the notion tools available to you through the Notion MCP Server?

Agent:

[15 tools called]

Here’s a summary of all the Notion MCP tools with their descriptions:


:open_book: Reading & Searching

Tool Description
notion-search Semantic search over Notion workspace and connected sources (Slack, Google Drive, GitHub, Jira, Microsoft Teams, Sharepoint, OneDrive, Linear). Supports filtering by creation date and creator. Also supports user search by name or email.
notion-fetch Retrieves details about a Notion entity (page or database) by URL or ID. Returns pages in enhanced Markdown format, databases return all data sources with schema.

:memo: Page Operations

Tool Description
notion-create-pages Creates one or more Notion pages with specified properties and content using Notion-flavored Markdown. Pages can be standalone, under a parent page, or in a database. Up to 100 pages per call.
notion-update-page Updates a page’s properties or content. Supports commands: update_properties, replace_content, replace_content_range, and insert_content_after.
notion-duplicate-page Duplicates a Notion page asynchronously. Returns the new page ID/URL immediately while duplication completes in background.
notion-move-pages Moves one or more pages or databases (up to 100) to a new parent (page, workspace, database, or data source).

:file_cabinet: Database Operations

Tool Description
notion-create-database Creates a new database with specified property schema. Supports property types: title, rich_text, number, select, multi_select, date, people, checkbox, url, email, phone_number, formula, relation, rollup, etc.
notion-update-database Updates a database’s properties, title, description, or display mode. Can add/rename/remove properties, change inline display, or move to trash.
notion-query-data-sources Query Notion databases using SQLite SQL or by executing a saved view. Supports parameterized queries, aggregations, filters, and cross-database joins.

:speech_balloon: Comments

Tool Description
notion-create-comment Adds a comment to a page with rich text formatting (bold, italic, mentions, links, etc.).
notion-get-comments Retrieves all comments from a specific page.

:busts_in_silhouette: Users & Teams

Tool Description
notion-get-self Retrieves the bot user associated with the current token.
notion-get-user Retrieves details about a specific user by their user ID.
notion-get-users Lists all users in the workspace (members and guests). Supports search by name/email and pagination.
notion-get-teams Lists teams (teamspaces) in the workspace with membership status, IDs, names, and roles. Supports filtering by name.

What are you experiencing? Where do you see truncated tool descriptions?

Sorry, maybe I didn’t explain it clearly. Actually what I meant was the description here.

Sorry, maybe I didn’t explain it clearly. Actually what I meant was the description here.

May I ask if the usage description of MCP Tool in Cursor has a token length limit? It seems that the lengthy description of Notion could be affected by this.

Ah. I see what you’re saying now.

I think two things are going on.

One, a UI bug with super-long MCP tool descriptions. At least for me, I see a scrollbar (I’m on v2.3.7). Unfortunately, I have no way to move my mouse into the description to actually let me scroll.

The other is that Cursor truncates tool descriptions to 6,500 characters. The notion-create-pages description is about 14,700 characters long.

Not too sure what to do here—we want to prevent MCP servers from flooding the context window. I’ll flag this for the team.

It was working fine a few days ago, and I’m wondering when this restriction was implemented.

Hey @shuo_liang

Dug into a bit more. It looks like improvements are being made to get around this character limit (and, overall, change how MCPs are read into the agent), but they’re behind a feature flag, and you may have fallen out of it.

This will get resolved for you, I’m just not sure exactly when!

Thanks for the update and clarification! Totally get that the full fix needs some time.

Just wondering if it’s possible to add me to the feature flag whitelist temporarily if the resolution takes a while? That would help me unblock my current work smoothly.

If you switch your Update Track to a Nightly build (Cursor Settings > Beta), I believe you’ll find yourself back behind the flag! But naturally, Nightly builds carry some risk.