No user-submitted related servers found.
Scored across 37 tools
Most tools map cleanly to a single resource+action (file, page, user, group, site, block, page version), and the content tools explicitly warn against using get-page-by-id for reading copy. However, there are two block delete tools (delete-block-from-page-area vs delete-block-by-id) with no guidance on which to use, and update-page-by-id vs update_page_content overlap in intent, as do get-page-by-id (with content includes) and get_page_content.
The dominant convention is kebab-case verb_noun (add-file, get-users, delete-page-by-id), which is readable and predictable. But two tools break it with snake_case (get_page_content, update_page_content), and a few tools lack the resource suffix pattern (get-account, get-system-info), so the set is mixed.
37 tools is heavy for a single CMS surface and well above the comfortable 3-15 range. While the resources are real, the page/block/page-version cluster in particular has accumulated many near-adjacent operations that inflate the surface.
Files, pages, users, blocks, and page versions all have solid create/read/update/delete lifecycles, including content read/write and sitemap traversal. Gaps remain: groups have add/get/list but no update or delete, and sites are entirely read-only (get-sites, get-site-by-id, get-default-site with no create/update/delete).