notion-agent-hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notion-readB | Read pages, databases, or blocks from Notion. Returns structured content including properties and child blocks. |
| notion-writeC | Create or update Notion pages. Supports creating pages with rich content blocks (headings, paragraphs, lists, toggles, code, callouts). |
| notion-queryA | Query a Notion database with filters and sorting. Returns matching pages with summarized properties. |
| web-searchA | Search the web for information. Uses Brave Search API if available, falls back to DuckDuckGo. Useful for research tasks. |
| code-runA | Execute JavaScript code in a sandboxed environment. Has access to Math, Date, JSON, and standard built-ins. No filesystem or network access. |
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 5 tools
Most tools are clearly distinct: code-run and web-search are unrelated to Notion, while notion-read and notion-query both deal with reading data but differ in scope—read fetches raw pages/blocks, query performs filtered database searches. The overlap is minor and descriptions clarify the intended use, so agents should rarely confuse them.
Three tools consistently use the 'notion-' prefix with a verb (read, write, query), but code-run and web-search break this pattern by omitting any prefix. The verbs themselves are clear, yet the mixed convention (prefixed and non-prefixed) makes the naming feel less predictable.
With only 5 tools, the set is compact and well-scoped for a Notion automation hub plus auxiliary capabilities. Each tool serves a distinct purpose without redundant overlaps, and the number is comfortably within the ideal 3-15 range.
The Notion tools cover read, write/update, and query, which covers most common CRUD operations, though database creation and deletion are missing. The inclusion of code execution and web search extends the surface well beyond basic Notion access, but the absence of a delete or list-all operation is a minor gap that agents can work around.