X MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| post_tweetC | Post a tweet to X (Twitter) |
| get_user_timelineC | Get the user's recent tweets |
| search_tweetsC | Search for tweets using a query |
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 3 tools
Each tool has a clearly distinct purpose: get_user_timeline retrieves a user's recent tweets, post_tweet creates a new tweet, and search_tweets finds tweets by query. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_user_timeline, post_tweet, search_tweets) with clear, descriptive verbs. The naming is uniform and predictable across the set.
With only 3 tools, the server feels slightly thin for a Twitter/X integration, as it lacks operations like deleting tweets, managing likes, or handling direct messages. However, it covers basic posting and reading, which is reasonable for a minimal scope.
The tools provide core read and write capabilities (get, post, search) but miss key Twitter/X features such as tweet deletion, like/unlike, retweeting, or user profile management. This leaves notable gaps that agents might need to work around for full functionality.