No user-submitted related servers found.
Scored across 72 tools
The tool set covers many distinct operations, but there is notable overlap in search-and-replace tools (search_replace_preview/execute vs. scoped_search_replace_preview/execute) and update tools (update_content vs. update_content_by_path vs. bulk_update_content). While descriptions help differentiate, an agent could misselect due to similar purposes.
Tool names follow a consistent snake_case pattern with clear verb_noun conventions (e.g., create_content, list_assets, delete_folder). There are no deviations in style, making the naming highly predictable and readable.
With 72 tools, the count is excessive for a CMS server, making it overwhelming and difficult to navigate. This many tools suggests over-fragmentation of operations, which could hinder agent usability and efficiency.
The tool set provides comprehensive coverage for content management, including CRUD operations for all entities (content, templates, assets, forks), bulk operations, versioning, search, and publishing workflows. No obvious gaps are present; it supports full lifecycle management.