No user-submitted related servers found.
Scored across 41 tools
Each tool targets a distinct resource and action: posts, users, lists, media, DMs, engagements, and status checks are cleanly separated. The only potentially confusable group is the three DM event listers, but their descriptions clarify scope (all, conversation, participant) well enough. Even similar read/write pairs like x_bookmarks_list vs x_bookmark_set are unambiguous.
Most tools follow an x_<resource>_<verb> pattern, but there are irregular deviations: x_search_recent/x_search_archive place the modifier after the verb, x_user_search uses noun+noun, x_lists_owned is a state not a verb, and x_timeline_home/mentions/user use scope as the final segment. The core convention is recognizable, but the inconsistencies would slow agent pattern recognition.
At 41 tools, this server is well past the 16-25 range that already feels heavy for most servers. The broad X API scope explains the count, but an agent would face a large selection surface with many near-adjacent operations that could have been consolidated (e.g., count queries, multiple timeline variants).
The surface covers the major X features: post CRUD, search, timelines, lists, media, DMs, social graph, engagements, and usage/status. Minor gaps exist—no read-side listing for likes, mutes, or blocks, and no list-follower enumeration—but these are workable and do not create dead ends for typical workflows.