AI-powered Notion workspace management tool with agentic chat, duplicate detection, garbage collection, dead link analysis, and sensitive data scanning
NoteRunway exposes 12 tools with significant definition gaps. Tool names lack consistent verb-noun structure (e.g., 'API-post-search', 'API-patch-block-children' are API-centric rather than action-centric). Descriptions vary widely in quality: some are adequate (search_pages, get_page_content), but many are generic or missing context (API-* tools lack descriptions entirely in visible code). Parameter schemas are present but sparse, most lack detailed type constraints, enums, or validation guidance. No output schemas documented. Error handling is minimal; no recovery guidance visible. The propose_actions tool has a complex discriminated union schema (good), but most tools lack comparable rigor. Overall, definitions would require significant refinement before production use.
Delete a block from Notion
Retrieve block children from a Notion page
Append or update block children in a Notion page
Update page properties in Notion
Create a new page in Notion
Search for pages in Notion workspace
Retrieve metadata of a specific Notion page
API-centric tool naming (API-post-*, API-patch-*, API-get-*, API-delete-*) violates verb-noun convention. LLMs cannot infer intent from 'API-post-search' vs 'search_pages'. Rename to action-centric names: create_page, update_page_blocks, delete_block, list_page_blocks.
Six API-* tools lack descriptions entirely (visible in route.ts). Add 50-150 char descriptions explaining WHAT each tool does, WHEN to use it, and any prerequisites.
Parameter descriptions are minimal or absent. E.g., 'block_id' in API-patch-block-children lacks context (is it a page ID or block ID?). 'filter' in API-post-search has no guidance on valid property/value pairs. Add format, range, and constraint hints to every parameter.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
Get the metadata of a specific Notion page by its ID
Read the actual block content (text, bullets, headings) of a Notion page
Propose write actions (archive, create, rename, append to, or replace page content) that require user approval before execution
Run a workspace analysis. Use "dead_links" to find pages with broken/orphaned links, "garbage" to find stale/empty pages, "workspace_stats" for a summary, or "sensitive_data" to scan all pages for accidentally stored secrets, passwords, API keys, tokens, and PII.
Search for pages in the Notion workspace by keyword or topic
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., page_id from create_page response). Document return types for all tools, especially those that produce IDs needed by chained tools.
Error handling is absent from visible tool definitions. No recovery guidance, error classification, or actionable messages. E.g., if delete_block fails, the LLM has no guidance on whether to retry, ask the user, or abort. Add error responses with recovery hints.