Loading ToolBench
Model Context Protocol (MCP) server for managing scheduled social media posts and content automation across multiple platforms
Two tools with partial schema coverage. timeline_add_scheduled_event has a comprehensive input schema with 8 parameters, enums for platform, and reasonable defaults, but the description embeds procedural instructions (use terminal tool, check existing tracks) that should be agent logic, not tool guidance. timeline_list_tracks has minimal description ('List all tracks') and basic pagination params. Neither tool documents output schemas. The server lacks error handling guidance, recovery paths, and security considerations around content generation and approval workflows.
Add a scheduled event to a track. IMPORTANT: 1) Use the terminal MCP tool to get the current date/time (execute_command("date")) before scheduling events to ensure correct dates. 2) ALWAYS use timeline_list_tracks first to check existing tracks - if a track with a similar name or purpose already exists, use that instead of creating a new one. If unsure whether an existing track matches your needs, ask the user for clarification before proceeding.
List all tracks
Tool descriptions embed procedural instructions instead of declarative purpose. timeline_add_scheduled_event's description tells the agent to 'Use the terminal MCP tool to get the current date/time' and 'ALWAYS use timeline_list_tracks first', these are agent orchestration concerns, not tool documentation. Descriptions should state WHAT the tool does, not HOW the agent should use it.
Output schemas are not documented. Neither tool specifies what fields are returned, their types, or structure. LLMs cannot plan downstream calls or extract required data (e.g., track IDs for chaining). This violates the documented output schema requirement.
timeline_list_tracks has a trivial description (7 words, under 20 chars of meaningful content). It does not explain when to call it, what structure it reveals, or how it fits into the workflow. Descriptions should be 10 - 1024 characters with context for selection.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If timeline_add_scheduled_event fails (invalid track, scheduling conflict, content generation error), the tool provides no actionable error message or next steps. Errors should categorize as retryable, user-fixable, or fatal.
Approval workflow lacks confirmation/dry-run pattern. timeline_add_scheduled_event schedules content for posting across social platforms with no confirmation step. Irreversible operations should support dry-run or explicit confirmation to prevent accidental posts.