tweetsave-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tweetsave_get_tweetA | Fetch a single tweet with all its content including text, media (photos, videos, GIFs), polls, and engagement metrics. This tool retrieves tweet data from Twitter/X using the FxTwitter API. It returns the tweet content, author info, media URLs, and engagement stats. Args:
Returns: Tweet data including:
Examples:
Note: Does not fetch replies. Use tweetsave_to_blog for a complete blog post with formatting. |
| tweetsave_get_threadA | Fetch a tweet thread (multiple connected tweets by the same author). Note: Current implementation fetches the main tweet. Full thread crawling requires additional API access. Args:
Returns: Array of tweets in the thread with all content and media. Examples:
|
| tweetsave_to_blogA | Convert a tweet into a formatted blog post with title, content, media, and metadata. This tool transforms a tweet into a readable blog post format, perfect for:
Args:
Returns: BlogPost with:
Examples:
|
| tweetsave_batchA | Fetch multiple tweets at once (max 10). Useful for:
Args:
Returns: Array of tweets or a combined feed in markdown format. Examples:
|
| tweetsave_extract_mediaA | Extract direct media URLs (photos, videos, GIFs) from a tweet. Returns direct URLs that can be downloaded or embedded. Video URLs are the highest quality available. Args:
Returns: List of media items with:
Examples:
|
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 5 tools
Each tool has a clearly distinct purpose: fetching single tweets, multiple tweets, threads, extracting media, and converting to blog format. There is no overlap or ambiguity in their intended use.
All tools share the 'tweetsave_' prefix and use snake_case. However, 'tweetsave_batch' is a noun form while others use verbs (get, extract, to), showing minor inconsistency.
With 5 tools, the server is well-scoped for its purpose of retrieving and converting tweets. Each tool earns its place without being excessive or insufficient.
Core retrieval and conversion operations are covered, but missing save-to-storage or search capabilities. The server name implies saving, yet no tool persists tweets locally.