Twitter241 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_about_accountD | Get About Account |
| get_community_detailsC | Get Community Details by Community ID |
| get_community_aboutC | Get Community About by Community Id |
| get_community_tweetsC | Get Community Tweets by Community ID |
| get_community_moderatorsA | Get Community Moderators by Community ID |
| get_community_timelineD | Explore Community Timeline |
| get_community_topicsC | Get Community Topics |
| fetch_popular_communityD | Fetch Popular Community |
| search_communityD | Search community |
| get_community_membersC | Get Community Members by Community ID |
| get_tweet_detailsB | Get Tweet Details By Tweet ID |
| get_post_comments_v2C | Get Post Comments By Post ID V2 |
| get_list_detailsC | Get list details by listId |
| get_list_timelineC | Get list timeline by listId |
| search_listsC | Search lists |
| get_highlightsC | Get user highlights by ID |
| get_user_followers_idsB | GET Followers IDs by Username |
| get_user_verified_followersC | Get User Verified Followers By ID. You can get the user(rest_id) query from \ |
| get_user_following_idsB | GET Following IDs by Username |
| get_user_followersC | Get User Followers By ID. You can get the user(rest_id) query from \ |
| get_user_followingsC | Get User Followings By ID. You can get the user(rest_id) query from \ |
| get_user_tweetsC | Get User Tweets By ID You can get the user(rest_id) query from \ |
| get_user_mediaD | Get User Media By ID You can get the user(rest_id) query from \ |
| get_user_replies_v2C | Get User Replies By ID You can get the user(rest_id) query from \ |
| get_user_by_usernameC | Gets a user by username |
| get_user_repliesC | Get User Replies By ID You can get the user(rest_id) query from \ |
| get_users_by_idsD | Get Users By IDs (Rest IDs) |
| get_users_by_ids_v2D | Get Users By IDs V2 |
| get_list_membersB | Get List Members by List ID |
| get_listB | Get List Followers by List ID |
| get_trends_by_locationD | Get Trends By Location |
| get_available_trends_locationsB | Get Available Trends Locations |
| get_post_quotesB | Get Post Quotes By Post ID |
| get_post_retweetsC | Get Post Retweets By Post ID |
| get_post_commentsC | Get Post Comments By Post ID |
| get_tweets_details_by_idsC | Get Tweets Details By Tweet IDs |
| get_tweet_details_v2C | Get Tweet Details By Tweet ID |
| job_detailsC | Get Job Details |
| search_jobsD | Search Jobs |
| search_job_locationsC | Suggest Job Locations |
| get_user_likesD | Get User Likes By ID You can get the user(rest_id) query from \ |
| search_twitter_v2C | Search Twitter (Top, Latest, Videos, Photos and People) |
| space_detailsC | Get Space Details By ID |
| get_organization_affiliatesD | Get Organization Affiliates By ID You can get the user(rest_id) query from \ |
| search_twitterB | Search Twitter (Top, Latest, Videos, Photos and People) |
| autocompleteC | Twitter Seach Query Autocomplete |
| get_post_likesB | Get Post Likes By Post ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 47 tools
Multiple tools appear to do the same thing (e.g., get_tweet_details and get_tweet_details_v2, get_users_by_ids and get_users_by_ids_v2, search_twitter and search_twitter_v2), with no clear distinction between versions. The naming of get_list vs get_list_details vs get_list_timeline also adds confusion, making it difficult for an agent to reliably select the correct tool.
Most tools follow a get_verb_noun pattern, but there are notable exceptions like autocomplete, job_details, space_details, and fetch_popular_community. The use of v2 suffixes is inconsistent, and some names are vague (e.g., get_about_account, get_list), so the pattern is not predictable across the set.
With 47 tools, the server is heavily bloated, especially given the redundant v2 pairs. This exceeds the threshold for a well-scoped tool set, and many tools could be consolidated or removed without losing functionality.
The server covers a broad range of read-only operations for Twitter data (users, tweets, communities, lists, trends, jobs, spaces), which is fairly complete for a retrieval-focused API. However, there are no write operations (create, update, delete) and some obvious gaps like user mentions or tweet posting, but these may be out of scope for the intended use.