No user-submitted related servers found.
Scored across 87 tools
Most tools target a distinct resource and action, and the descriptions generally clarify intent, but several clusters overlap: update_provider_settings duplicates the dedicated set_provider_* tools, update_keyword overlaps set_keyword_target_url, and the API key/personal token creation tools are easy to confuse. With 87 tools, these ambiguous boundaries create a real risk of an agent selecting the wrong operation.
The server consistently uses snake_case verb_noun naming with recognizable patterns like list_, create_, update_, delete_, get_, set_, and enable_/disable_. Minor deviations exist—load_more_backlink_rows, sync_project_traffic, run_rank_check, research_keywords, and list_sitemap_monitors being plural for a single monitor—but the overall convention is predictable.
At 87 tools, the surface is far beyond what an agent can efficiently navigate; the rubric treats 50+ tools as an extreme mismatch. While the tools cover a broad product, the sheer count creates significant selection overhead, prompt bloat, and higher risk of choosing the wrong tool.
The tool surface is very broad and covers lifecycle operations for projects, keywords, rank checks, backlinks, providers, webhooks, alerts, team management, API keys, saved views, competitors, and migration. Minor gaps exist—no single-item getters for webhooks/providers/alert rules, no update_saved_view, and no update/create for sitemap monitors—but list endpoints and intentional lifecycle choices make these workable.