Loading ToolBench
The most comprehensive WordPress MCP server - 145 production-ready tools for complete WordPress management with AI
This server has 12 tools across Astra theme and WordPress comments domains. All tools have descriptions and explicit input schemas visible in the source. However, descriptions are generic and parameter-level documentation is sparse. Output schemas are not documented at all, there is no evidence of what these tools return. Error handling is not visible in the source code provided. The naming follows verb-first conventions (get_, create_, update_, enable_, disable_), which is good, but several tools operate on the same resources with similar names (e.g., get_custom_layout vs get_custom_layouts, create_comment vs update_comment) without clear distinctions in the descriptions. Security posture is unclear, the 'site' parameter suggests multi-tenant support, but there is no documentation of how authentication or authorization is handled. The server claims 145 production-ready tools but only 12 are visible in the source, limiting evaluation scope.
Create a new Astra custom layout. Create custom headers, footers, or hook-based layouts with conditional display rules.
Disable Astra mega menu for a menu item. Reverts the menu item to standard dropdown behavior.
Enable Astra mega menu for a menu item with default settings. Quick way to turn a regular menu item into a mega menu.
Get a specific Astra custom layout by ID. View configuration, content, and display rules.
Get all Astra custom layouts (headers, footers, hooks). List all conditional layout overrides.
Get Astra mega menu configuration for a specific menu item. Shows columns, content, and display settings for advanced dropdown menus.
Vague 'data' parameter in 5 tools (update_mega_menu, create_custom_layout, update_custom_layout, create_comment, update_comment). No documentation of required fields, nested structure, or validation rules. LLMs cannot infer what payload structure is expected.
No output schemas documented for any tool. LLMs cannot plan downstream tool calls or extract required fields (e.g., does get_mega_menu return menu_item_id? Does get_comments return total count for pagination?). Required for proper tool chaining.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 50 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 48 | - | v1 |
Update an existing Astra custom layout. Modify content, display rules, or settings.
Create or update Astra mega menu configuration. Configure columns, content, display mode, and styling for advanced dropdown menus.
Create a new comment on a post. Requires post ID and comment content.
Get a single comment by ID. Retrieve detailed information about a specific comment.
Get a list of comments with optional filters. Retrieve comments by post, author, status, date range, and more.
Update an existing comment. Modify comment content, author info, or status.
get_comments accepts an undocumented 'filters' parameter (object type). No description of what filter keys are supported (e.g., post_id, author, status, date_range?). Ambiguous parameter makes tool selection and usage uncertain.
No error handling guidance visible in schemas or descriptions. Tools do not document retryable vs. fatal errors, actionable error messages, or recovery steps. If a create_comment fails, LLM has no guidance on what to do next.
Multi-parameter tools like enable_mega_menu have only 1 required parameter (menu_item_id); 'columns' has a default of 3. No documentation of whether defaults are safe or explain why these are optional. Agents may not know when to override defaults.
No documentation of 'site' parameter semantics across all tools. Is it a domain name, site ID, or slug? How are multi-site installations handled? Are all sites equally accessible or are there permission boundaries? Critical for security and multi-tenant setup.