No user-submitted related servers found.
Scored across 16 tools
Most tools have a clearly distinct purpose: the kb_* family is retrieval, audit_work/analyze_landing_page/analyze_ads/growth_audit/intel_report are distinct audit products, and job_status/credits_balance are operational. However, audit_work (which explicitly accepts a landing page or ads as input) overlaps conceptually with analyze_landing_page and analyze_ads, and kb_get with an optional section parameter partly overlaps with kb_examples. The credit prices and depth/focus descriptions do help an agent disambiguate, but the choice is not always obvious.
There is a readable two-family structure: a kb_ snake_case namespace for knowledge-base retrieval and an unprefixed family for audits and account ops. But within the unprefixed family the convention flips between verb_noun (audit_work, list_reports, get_report, analyze_landing_page, analyze_ads) and noun_noun (job_status, credits_balance, growth_audit, intel_report). Everything is snake_case so it scans fine, but the verb placement is not predictable.
At 16 tools this sits at the upper edge of a comfortable set, but each tool maps to a distinct capability (seven free/cheap KB lookups, five paid audits of different scope, plus job and credit handling). Nothing looks redundant enough to cut, though the pricey audit tier could plausibly be consolidated.
The surface covers the full lifecycle: discovery (kb_sectors, list_reports, kb_search), retrieval by id/section (kb_get, kb_examples, get_report), benchmarks and guidance (kb_benchmarks, kb_brief, kb_playbook), analysis at several depths (audit_work through intel_report), plus async job polling and credit pricing. No dead ends for the stated audit-and-knowledge-base purpose.