Twitter

1---2name: twitter3version: 1.4.04description: "Twitter/X (x.com) data lookup \u2014 fetch tweets by URL or ID, search\5  \ tweets, user profiles, followers, replies. Use for ANY x.com or twitter.com URL."6tools:7- twitter_search_tweets8- twitter_get_tweets9- twitter_user_info10- twitter_user_tweets11- twitter_user_followers12- twitter_user_followings13- twitter_tweet_replies14- twitter_tweet_retweeters15- twitter_search_users16- twitter_get_article17- twitter_tweet_thread_context18- twitter_tweet_quote19- twitter_get_trends20metadata:21  starchild:22    emoji: "\U0001F426"23    skillKey: twitter24    requires:25      env:26      - TWITTER_API_KEY27user-invocable: false28disable-model-invocation: false29---30 31## 🔴 HARD LIMITS — READ FIRST32> **⛔ CALL AT MOST 3 TWITTER TOOLS PER RESPONSE. STOP AFTER 3 CALLS.**33> After each tool call, check: "Do I have enough data to answer?" If yes → STOP AND REPLY.34> **⛔ NEVER call `bash` or `write_file` for any twitter task** — reason inline, no scripts.35> **⛔ NEVER paginate unless user explicitly asks for more** — first page is enough.36> **⛔ NEVER call `lunar_coin`, `lunar_coin_time_series`, or any LunarCrush/CoinGecko tool** — Twitter sentiment 问题只用 `twitter_search_tweets` 回答，不跨 skill。37> **⛔ NEVER call `coin_price`, `cg_trending`, `cg_coins_markets`** — 价格数据超出 Twitter skill 范围。38 39## 🔗 URL Handling — x.com / twitter.com40> **⛔ NEVER use `web_fetch` for x.com or twitter.com URLs** — Twitter blocks scraping, you'll only get a login wall.41> **✅ ALWAYS extract the tweet ID from the URL and use `twitter_get_tweets`.**42 43| URL pattern | Extract | Tool call |44|-------------|---------|-----------|45| `x.com/{user}/status/{id}` | tweet ID = `{id}` | `twitter_get_tweets(tweet_ids=["{id}"])` |46| `twitter.com/{user}/status/{id}` | tweet ID = `{id}` | `twitter_get_tweets(tweet_ids=["{id}"])` |47| `x.com/{user}` | username = `{user}` | `twitter_user_info(username="{user}")` |48 49**Example:** User sends `https://x.com/zerohedge/status/2042670029548794219`50→ Extract ID: `2042670029548794219`51→ Call: `twitter_get_tweets(tweet_ids=["2042670029548794219"])`52→ Never: `web_fetch("https://x.com/...")`53 54## 💡 Few-Shot Examples55**Q: 找 3 个关于 BTC ETF 的高赞推文，只要 ID 和点赞数**56→ PLAN: 1 call `twitter_search_tweets("BTC ETF min_faves:100")` → pick top 3 from results → reply JSON57→ STOP after 1 call. Total tools: 158 59**Q: @elonmusk 最近发的推文哪条点赞最多？只要数字**60→ PLAN: 1 call `twitter_user_tweets("elonmusk")` → find max likes in results → reply number61→ STOP after 1 call. Total tools: 162 63**Q: 搜索 solana 推文，找点赞最多那条的作者**64→ PLAN: 1 call `twitter_search_tweets("solana")` → find tweet with most likes → extract username65→ STOP after 1 call. Total tools: 166 67**Q: 对比 @A 和 @B 谁粉丝多，再看粉丝多的最新推文**68→ PLAN: call `twitter_user_info("A")` + `twitter_user_info("B")` → determine winner → call `twitter_user_tweets(winner)`69→ Total tools: 3. STOP.70 71## ⚡ FAST PATHS (act immediately, no clarification needed)72| Trigger keywords | Action |73|-----------------|--------|74| x.com or twitter.com URL with `/status/{id}` | Extract tweet ID → `twitter_get_tweets(tweet_ids=["{id}"])` — **never web_fetch** |75| x.com or twitter.com URL with `/{username}` only | Extract username → `twitter_user_info(username="{username}")` |76| crypto sentiment / 情绪扫描 / market mood / BTC ETH SOL 讨论 | Call `twitter_search_tweets` once per coin: `"$BTC"`, `"$ETH"`, `"$SOL"` — summarize tone, **no user profile lookups** |77| search tweets about X | Call `twitter_search_tweets` with the topic |78| who is @username | Call `twitter_user_info` |79| what did @username post | Call `twitter_user_tweets` |80 81## Tool Decision Tree82**"Search for tweets about a topic"** → `twitter_search_tweets`83Advanced query with operators: keywords, from:user, #hashtag, $cashtag, min_faves, date ranges.84 85**"Look up a specific tweet or set of tweets"** → `twitter_get_tweets`86Pass one or more tweet IDs directly.87 88**"Who is this Twitter account?"** → `twitter_user_info`89Profile data: bio, follower count, tweet count, verification.90 91**"What has this account been posting?"** → `twitter_user_tweets`92Recent tweets from a specific user.93 94**"Who follows this account?"** → `twitter_user_followers`95List of followers for a user.96 97**"Who does this account follow?"** → `twitter_user_followings`98List of accounts a user follows.99 100**"What are people saying in reply to this tweet?"** → `twitter_tweet_replies`101Replies to a specific tweet by ID.102 103**"Who retweeted this?"** → `twitter_tweet_retweeters`104Users who retweeted a specific tweet.105 106**"Find accounts related to a topic"** → `twitter_search_users`107Search users by name or keyword.108 109**"Read a long X article"** → `twitter_get_article`110Pass the article tweet ID. Returns title, preview, cover, and content blocks.111 112**"Get full thread context"** → `twitter_tweet_thread_context`113One call returns parent chain + direct replies for the target tweet.114 115**"Who quoted this tweet?"** → `twitter_tweet_quote`116Get quote tweets for a specific tweet ID.117 118**"What is trending now?"** → `twitter_get_trends`119Get trends with optional `woeid`, `country`, `category`, `limit`.120 121**"Crypto sentiment scan / 情绪扫描 / market mood"** → `twitter_search_tweets` (call once per coin)122For BTC/ETH/SOL sentiment: search `"$BTC"`, `"$ETH"`, `"$SOL"` separately, then summarize tone inline.123⛔ NEVER call `twitter_user_info`, `twitter_user_followers`, or `twitter_user_tweets` during a sentiment scan — text analysis only.124 125## Available Tools126| Tool | Description | Key Params |127|------|-------------|------------|128| `twitter_search_tweets` | Advanced tweet search | `query` (required), `cursor` |129| `twitter_get_tweets` | Get tweets by ID | `tweet_ids` (array, required) |130| `twitter_user_info` | User profile lookup | `username` (required) |131| `twitter_user_tweets` | User's recent tweets | `username` (required), `cursor` |132| `twitter_user_followers` | User's followers | `username` (required), `cursor` |133| `twitter_user_followings` | User's followings | `username` (required), `cursor` |134| `twitter_tweet_replies` | Replies to a tweet | `tweet_id` (required), `cursor` |135| `twitter_tweet_retweeters` | Who retweeted | `tweet_id` (required), `cursor` |136| `twitter_search_users` | Search for users | `query` (required), `cursor` |137| `twitter_get_article` | Get long-form article | `tweet_id` (required) |138| `twitter_tweet_thread_context` | Get full thread context | `tweet_id` (required) |139| `twitter_tweet_quote` | Get quote tweets | `tweet_id` (required), `cursor` |140| `twitter_get_trends` | Get trends | `woeid`, `country`, `category`, `limit` |141 142## Usage Patterns143### ⚠️ Token Budget Rules144- Sentiment scan: max **3 `twitter_search_tweets` calls** (one per coin), then summarize. Stop.145- Account research: max **2 tool calls total** unless user asks for more depth.146- Never chain more than 5 Twitter tool calls in one response.147 148### Research an account1491. `twitter_user_info` — get profile, follower count, bio1502. `twitter_user_tweets` — see what they've been posting1513. `twitter_user_followings` — who they follow (reveals interests)152 153### Track a topic or token1541. `twitter_search_tweets` with query like `"$SOL min_faves:50"` — find popular tweets1552. `twitter_search_users` with the topic — find relevant accounts156 157## Output Constraints (IMPORTANT for small models)158- **Max 1 `twitter_search_tweets` call per coin/topic** — do not repeat searches for same query. First result set is sufficient.159- **Max 3 `twitter_user_info` calls per response** — only look up the most relevant accounts.160- **Never call `bash` or `write_file` for Twitter data** — reason inline directly from tool results.161- **Sentiment summaries**: after 1 search call, summarize tone inline in 3–5 sentences. Done.162- **Pagination**: only fetch next page if user explicitly asks for more results.163- **After getting search results: sort/filter in your head, do not call bash to sort.**164 165### Analyze engagement on a tweet1661. `twitter_get_tweets` — get the tweet and its metrics1672. `twitter_tweet_replies` — see the conversation1683. `twitter_tweet_retweeters` — see who amplified it169 170### Find influencers in a space1711. `twitter_search_users` with keyword (e.g. "DeFi analyst")1722. `twitter_user_info` on top results to compare follower counts1733. `twitter_user_tweets` to check content quality174 175## Search Query Operators176The `twitter_search_tweets` tool supports advanced operators:177 178| Operator | Example | Description |179|----------|---------|-------------|180| keyword | `bitcoin` | Tweets containing the word |181| exact phrase | `"ethereum merge"` | Exact phrase match |182| `from:` | `from:elonmusk` | Tweets by a specific user |183| `to:` | `to:elonmusk` | Tweets replying to a user |184| `#hashtag` | `#crypto` | Tweets with hashtag |185| `$cashtag` | `$BTC` | Tweets with cashtag |186| `lang:` | `lang:en` | Filter by language |187| `has:media` | `has:media` | Tweets with images/video |188| `has:links` | `has:links` | Tweets with URLs |189| `is:reply` | `is:reply` | Only replies |190| `min_faves:` | `min_faves:100` | Minimum likes |191| `min_retweets:` | `min_retweets:50` | Minimum retweets |192| `since:` | `since:2024-01-01` | Tweets after date |193| `until:` | `until:2024-12-31` | Tweets before date |194 195Combine operators: `from:VitalikButerin $ETH min_faves:100 since:2024-01-01`196 197## Pagination198Most endpoints support cursor-based pagination. When a response includes a cursor value, pass it as the `cursor` parameter to get the next page. If no cursor is returned, you've reached the end.199 200## Notes201- **API key required**: Set `TWITTER_API_KEY` environment variable. Tools will error without it.202- **Read-only**: These tools only retrieve data. No posting, liking, or following.203- **Usernames**: Always pass without the `@` prefix (e.g. `"elonmusk"` not `"@elonmusk"`).204- **Tweet IDs**: Use string format for tweet IDs to avoid integer overflow issues.205- **Rate limits**: The API has rate limits. If you get rate-limited, wait before retrying.