mcp-twitterio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TWITTER_API_KEY | Yes | Your Twitter API key from twitterapi.io |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_info_by_usernameA | 根据用户名Handle获取用户信息 |
| batch_get_users_by_idsA | 根据用户ID批量获取用户信息 |
| get_user_last_tweetsB | 获取用户最新的推文 |
| get_user_followersA | 获取用户的粉丝列表 |
| get_user_followingsA | 获取用户的关注列表 |
| get_user_mentionsA | 获取用户的提及 |
| get_tweets_by_idsA | 通过推文ID获取推文 |
| get_tweet_repliesA | 获取推文的回复 |
| get_tweet_quotationsA | 获取引用推文的推文 |
| get_tweet_retweetersA | 获取转发推文的用户 |
| advanced_search_tweetsA | 高级搜索推文 |
| get_list_tweetsA | 获取列表中的推文 |
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 12 tools
Each tool targets a distinct Twitter resource or action, making most boundaries clear. However, get_user_last_tweets and get_user_mentions could be confused without careful reading of descriptions, as both relate to user-centric tweets.
Most tools follow a get_<object>_<detail> pattern, but there are notable deviations like batch_get_users_by_ids, advanced_search_tweets, and get_list_tweets that disrupt consistency. The convention is readable but not uniformly applied.
With 12 tools, the server is well-scoped for a read-only Twitter API client. Each tool covers a distinct operation, and the count is within the ideal range without feeling excessive or insufficient.
The server covers a broad range of Twitter read operations: user info, tweets, interactions (replies, quotes, retweets), followers/followings, mentions, search, and list tweets. Minor gaps exist (e.g., user likes, trending topics), but core workflows are well covered.