Loading ToolBench
A workflow automation service that processes Notion pages, generates AI content using Gemini, and publishes to multiple platforms (DEV.to, Hashnode, Medium). Integrates with Notion MCP server for page management.
DevRel Empire exposes 3 tools with critical definition gaps. All three tools lack proper input schemas with type definitions and descriptions for individual parameters. Tool names use API-prefixed naming (API-post-search, API-patch-page, API-create-a-comment) rather than action-verb conventions. Descriptions are present but generic, lacking WHEN/WHY guidance. Parameter objects are documented at a high level but lack granular field-level descriptions. No output schemas are documented. Error handling is absent from tool definitions. This server appears to wrap Notion API calls without proper MCP tool abstraction.
Post published links back to a Notion page as a comment using the official Notion MCP server tool.
Update Status and cover image on a Notion page using the official Notion MCP server tool.
Search Notion pages using the official Notion MCP server tool. Executes structured search with filters and sorting options.
Tool names violate verb_noun convention. 'API-post-search', 'API-patch-page', 'API-create-a-comment' use API-prefixed naming and HTTP verbs instead of action verbs. Should be 'search_notion_pages', 'update_page_status', 'add_page_comment'.
Input schemas lack granular parameter descriptions. 'filter' and 'sort' parameters in API-post-search are documented as objects with examples in descriptions, but individual fields (value, property, direction, timestamp) lack type definitions and constraints. LLMs cannot infer valid field names or types.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., page_id from search results needed for update_page). Violates pattern:tool requirement for documented return types.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
Descriptions lack WHEN/WHY context. 'Search Notion pages using the official Notion MCP server tool' does not explain when to call this vs other discovery tools, what the typical use case is, or what structure is returned. Descriptions should be 50-200 chars with actionable guidance.
No error handling guidance in tool definitions. No indication of retryable vs fatal errors, no recovery suggestions, no validation rules for parameters. LLMs cannot self-correct on invalid input.