No user-submitted related servers found.
Scored across 28 tools
Most tools have distinct purposes targeting different Twitter/X resources (e.g., user_info vs. tweet_info vs. communities_search), but there is some functional overlap that could cause confusion. For example, 'followers' and 'list_followers' both retrieve follower lists but for different entities, while 'check_follow' and 'check_retweet' have similar verification logic but for different actions, potentially leading to misselection if not carefully read.
The naming is inconsistent with mixed conventions: some use snake_case (e.g., 'user_info', 'tweet_info'), others use camelCase (e.g., 'profiles_by_restids'), and some are verbose or unclear (e.g., 'comunity_posts' with a typo, 'communities_posts_search_latest'). There is no predictable pattern like verb_noun throughout, making it harder to navigate and understand the tool set at a glance.
With 28 tools, the count is too high for a typical MCP server, leading to potential bloat and complexity. While Twitter/X is a broad domain, many tools could be consolidated (e.g., multiple search and retrieval functions) or omitted to streamline the interface, making it feel heavy and less user-friendly for agents.
The tool set covers a wide range of Twitter/X functionalities, including user profiles, tweets, communities, lists, searches, and media, with good CRUD-like coverage for retrieval and verification. However, there are minor gaps, such as lack of tools for creating or modifying content (e.g., posting tweets, managing lists), which limits full lifecycle operations but still supports most read and search workflows effectively.