No user-submitted related servers found.
Scored across 60 tools
Tools map to distinct resources and lifecycle stages, and the descriptions explicitly disambiguate overlapping measurements (search performance vs AI traffic vs sources vs answers) and artifacts (public report vs brand analysis). A few pairs still overlap in practice—get_integrations_status vs get_google_status, and the four bot-visit/crawl tools—so an agent may hesitate, but the boundaries are documented.
All tools are snake_case and verb-first, with predictable families (list_, get_, create_, update_, delete_, set_, generate_, create_/get_ for async artifacts). Minor verb variation such as read_help_article, count_bot_visits and upsert_prompt_group is semantic and consistent within each family.
60 tools is far above a manageable set for an agent, even for a broad platform. Many read/status tools could be consolidated, and the sheer size materially increases tool-selection burden.
Core workflows are well covered: project/prompt tracking, metrics, content lifecycle, audits, topical maps, public reports and help. Some lifecycle gaps remain—no project deletion/archive, no category update/delete, no article or topical-map deletion, and prompt deletion is replaced by pausing—but agents can work around them.