No user-submitted related servers found.
Scored across 28 tools
Most tools have clearly distinct scopes, and the descriptions explicitly cross-reference siblings ('use metrics for account-wide totals, campaign_results for one campaign, list_campaigns for every campaign'). However, the cluster of count-returning tools (campaign_results, metrics, list_campaigns) and the status-returning pair (infrastructure_status, account) rely heavily on descriptions rather than obvious surface distinctions, so an agent could misselect on names alone.
Naming mixes multiple conventions: bare nouns (inbox, thread, metrics, account, activity), verb_noun (launch_campaign, update_lead, suppress_lead, remove_mailboxes), list_ prefixes (list_campaigns, list_leads, list_messages), and get_/configure_ pairs (get_dashboard/configure_dashboard, get_webhooks/configure_webhook, get_byo_domains/configure_byo_domain). The families are internally consistent and readable, but there is no single predictable pattern across the set.
At 28 tools this is on the heavy side, but the platform's apparent scope is genuinely broad: infrastructure provisioning, campaign lifecycle, inbox triage, lead management, webhooks, dashboards, BYO domains, and operator messaging. Each tool occupies a distinct functional slot with minimal redundancy, so the count is justified for the domain.
The core lifecycle is well covered: provision infrastructure, launch/pause campaigns, monitor results, triage replies, manage leads, and downgrade. Missing pieces are mostly deliberate and documented (no resume for paused campaigns, no un-suppress for leads, no campaign edit/delete), and agents can work around them; the absence of a campaign update tool and a manual lead-create path are minor gaps.