No user-submitted related servers found.
Scored across 129 tools
Most tools target clearly distinct resources, but several clusters create real ambiguity: the fork tools (create_fork/fork_page/merge_fork) vs the sandbox tools (start_agent_sandbox/end_agent_sandbox) describe the same underlying mechanism, search_replace_execute vs scoped_search_replace_execute vs preview variants overlap, and update_content vs update_content_by_path vs bulk_update_content compete for the same job. Detailed descriptions help, but an agent still has to reason carefully about which of several near-duplicates to pick.
Names overwhelmingly follow a predictable verb_noun snake_case pattern (list_content, get_content, create_content, update_content, delete_content), with parallel families for templates, folders, collections, snippets, redirects, webhooks, and approvals. Minor deviations exist — get_theme_version (singular) alongside get_theme_versions, force_unlock_content vs acquire/release_content_lock, and import_csv/import_markdown — but they remain readable and semantically consistent.
129 tools is excessive even for a broad CMS domain, far past the 50+ 'extreme mismatch' threshold. Many operations could be consolidated (e.g., separate lock get/acquire/release/force, singular/plural version getters, three publish paths), so each tool does not clearly earn its place.
The surface is remarkably complete: full content CRUD plus versions, soft-delete/restore, drafts/publish/scheduling, locks, comments, templates/fields, folders, collections, snippets, themes with versioning, assets, webhooks, redirects, imports, approval workflows, forks/sandbox staging, SEO/IndexNow, maintenance scans, and audit logs. Almost no lifecycle gap is left uncovered.