Related Servers

Most tools map to a single resource+action (niche keywords, rank radar data, tags, spaces/labels, alerts) and descriptions explicitly cross-reference siblings to steer selection. A few clusters are close enough to invite error — create_niche_dive vs create_niche_dive_from_competitors_list vs redive_niche, run_fast_keywords vs refresh_fast_keywords, and add_niche_keywords vs add_rank_radar_search_terms — but each description spells out the boundary, so selection is generally reliable.

Uniform snake_case verb_noun pattern throughout: list_/get_/create_/add_/remove_/pause_/resume_/delete_ plus a resource noun, consistently named per resource. Even the unusual verbs (redive_niche, generate_listing_copy) fit the same shape, and paired operations (add/remove_niche_spaces, pause/resume_rank_radar) are named symmetrically.

54 tools is heavy for any single server and far above the 3-15 range; while the domain (niches, rank radars, tags, fast keywords, PPC, inventory, alerts, billing) is broad, much of the surface is granular CRUD that could be consolidated. The add/remove pairs for spaces, labels, tag search terms, keyword exclusions, and search terms each consume two slots for one conceptual operation.

Coverage is strong: full lifecycle for niches, rank radars, tags, keywords and exclusions, plus async dive polling, PPC/SQP/inventory data, alerts, quota and usage auditing. However, several operations referenced in descriptions have no dedicated tool — the niche Outliers and Residue lists are only reachable indirectly via add/remove_niche_keywords origins, and there is no niche rename/relabel or fast-keywords delete.