Skip to main content
Glama
krishna-paulraj

X MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 3 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues