No user-submitted related servers found.
Scored across 82 tools
Many tools overlap in purpose: get_account_health, get_session_status, get_account_safety, get_metrics, and get_runtime_info all report account or server state, while get_profile, get_profile_posts, get_profile_context, search_profile, get_tweet, and prepare_reply all read profile/tweet context. With 82 tools, an agent can easily select a related but wrong read or write path, even though the descriptions attempt guidance.
All names use snake_case and are overwhelmingly verb_noun or verb_object (get_account_health, approve_draft, list_leads, add_proxy, remove_account). Minor deviations like engage, run_cycle, reply_to_tweet, and upsert_lead do not break the overall pattern. The naming is highly predictable.
82 tools is far beyond a well-scoped set; the domain is broad, but this many entry points imposes severe selection load and suggests redundant granularity. Per the rubric, 50+ tools is an extreme mismatch.
The surface covers accounts, proxies, drafts, queue, tweets, DMs, profiles, campaigns, leads, threads, analytics, and notifications with create/read/update/delete-style operations throughout. Minor asymmetries remain, such as no direct like/retweet alongside unlike_tweet/undo_retweet and no campaign/lead deletion, but these are workable.