notion-mcp has 12 tools with mixed definition quality. Strong points: most tools have descriptions and risk classifications. Critical gaps: NO visible input schemas for ANY tool (not in provided source), parameter details are minimal, output schemas undocumented, error handling missing. Tool naming follows verb_object convention (search, get_page_content, create_page, update_block, delete_block, archive_page) which is good. However, lack of schema visibility is a hard blocker, cannot verify parameter types, constraints, or completeness. Description quality varies: some tools (create_calendar_entry, create_expense_entry) have detailed descriptions (>200 chars) with good context; others (search, get_page_content) lack descriptions entirely in the visible source. No evidence of error recovery guidance, validation, or LLM-friendly error messages. The server provides no pagination hints for list/search operations. Tools like 'search' and 'get_page_content' are missing descriptions that would guide LLM selection.
Creates a new entry in a Notion data source designed as a calendar. This differs from CreatePageCall because it creates a page with a data source parent and must conform to the schema (Name, Date, Tags, etc.) Tags in this implementation use Multi-select properties, which allow applying multiple tags to a single entry (e.g., "Work", "Important", "Meeting" all on one entry).
Creates a new entry in a Notion expense tracker. This tool adds expense records with properties like title, amount, date, and category relation. The structure matches typical expense tracking data sources.
NO input schemas visible in source code for 8 of 12 tools (search, get_page_content, get_page_link, create_page, update_block, append_page, delete_block, archive_page).
Missing descriptions for 8 of 12 tools. LLMs cannot determine when or why to select these tools.
No output schemas documented. LLMs cannot plan downstream tool calls or understand what fields to extract. Critical for composability.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 31 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 36 | - | v1 |
Query records from a connected external data source.
Retrieve metadata for a connected data source. Fetches essential information about a Notion data source: ID, name, timestamps, parent, and schema properties.
Destructive operations (delete_block, archive_page) have NO confirmation/dry-run pattern. Agents can destroy data without verification.
No error handling or recovery guidance visible. LLMs receive raw API errors with no actionable recovery steps.
query_data_source has 'query' parameter marked nullable with no description of expected query structure or syntax. LLMs cannot construct valid queries.
No pagination support visible for search or query_data_source. Large result sets will blow context window and degrade LLM reasoning.
create_calendar_entry and create_expense_entry accept emoji icons as strings with no validation or constraint. LLMs may pass invalid emoji or multi-character strings.