Related Servers

Each tool has a clearly distinct data source or action: research_keyword_volume, research_backlinks, research_brand_lookup, research_competitor_ads each target different data. The only mild overlaps are research_domain_overview vs gsc_overview (any domain vs own site) and research_competitors vs research_domain_overview, but descriptions clearly disambiguate them. The trace/report workflow tools (start_trace, get_trace, search_reports, read_report, unlock_report) form a coherent pipeline rather than duplicating each other.

Most tools follow a prefix_verb/noun convention with meaningful families (research_*, gsc_*, site_audit_*), which aids grouping. However, standalone tools (get_trace, start_trace, read_report, search_reports, unlock_report) use a different verb-first style, and backlink_directories is a bare noun among verb-led names. Consistent within families but mixed overall.

17 tools is slightly heavy but each earns its place across three coherent areas (external research, growth reports, and the user's own site analytics). No obviously redundant tools, and the async poll pairs (start_trace/get_trace, site_audit_start/site_audit_get) are justified. Just on the edge of the comfortable 3-15 range.

Strong lifecycle coverage: keyword/backlink/competitor/ads/brand research, growth-report search-trace-read-unlock flow, real Search Console data, and site auditing with start/poll. Minor gaps: no explicit tool for acting on insights beyond auditing (e.g. drafting/publishing content) and no report deletion or account-management surface, but core research and verification workflows are fully covered.