Notion Advisor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_API_KEY | Yes | Your Notion internal integration token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search across all pages and databases in the workspace. Use when user wants to find content by keyword or title. |
| get_pageA | Retrieve a page's properties and metadata. Use when user wants to view page details or check properties. |
| create_pageB | Create a new page in a database or as a child of another page. Use when user wants to add new content to Notion. |
| update_pageA | Update a page's properties (not content blocks). Use when user wants to modify page metadata or database properties. |
| get_page_contentB | Retrieve all content blocks from a page. Use when user wants to read the full content of a page. |
| append_blocksA | Add new content blocks to a page or block. Use when user wants to add content to an existing page. |
| update_blockA | Update an existing block's content. Use when user wants to modify specific content. |
| delete_blockA | Delete a block (archive it). Use when user wants to remove content from a page. |
| get_databaseA | Retrieve database schema and properties. Use when user wants to understand database structure. |
| query_databaseA | Query a database with optional filters and sorts. Use when user wants to retrieve specific entries from a database. |
| create_databaseA | Create a new database as a child of a page. Use when user wants to set up a new structured data collection. |
| list_usersA | List all users in the workspace. Use when user needs to reference team members. |
| get_userA | Get details about a specific user. Use when user needs info about a team member. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct resource-action combination: pages vs. databases vs. blocks vs. users, and retrieval vs. creation vs. update vs. deletion. Even similar tools like get_page and get_page_content are clearly separated by properties/metadata vs. content blocks.
Most tools follow a clear verb_noun pattern like get_page, create_database, update_block, and delete_block. Minor deviations include the bare 'search' and 'query_database' instead of something like 'search_pages' or 'get_database_entries', but the overall style is predictable.
Thirteen tools is well-scoped for a Notion server covering pages, databases, blocks, search, and users. Each tool maps to a meaningful Notion API operation without excessive overlap or unnecessary surface area.
The core lifecycle for pages, blocks, and databases is represented: create, read, update, delete/archive, plus query and search. Minor gaps exist such as no update_database operation or a dedicated delete_page, though update_page may cover archiving.