home / skills / composiohq / awesome-claude-skills / twitter-automation

twitter-automation skill

/twitter-automation

This skill automates Twitter/X tasks using Composio's Rube MCP toolkit to create posts, search, manage bookmarks, lists, and media workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill twitter-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
8.8 KB
---
name: twitter-automation
description: "Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Twitter/X Automation via Rube MCP

Automate Twitter/X operations through Composio's Twitter toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/twitter](https://composio.dev/toolkits/twitter)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Twitter connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `twitter`
- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

## Setup

**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.


1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `twitter`
3. If connection is not ACTIVE, follow the returned auth link to complete Twitter OAuth
4. Confirm connection status shows ACTIVE before running any workflows

## Core Workflows

### 1. Create and Manage Posts

**When to use**: User wants to create, delete, or look up tweets/posts

**Tool sequence**:
1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user info [Prerequisite]
2. `TWITTER_UPLOAD_MEDIA` / `TWITTER_UPLOAD_LARGE_MEDIA` - Upload media [Optional]
3. `TWITTER_CREATION_OF_A_POST` - Create a new post [Required]
4. `TWITTER_POST_LOOKUP_BY_POST_ID` - Look up a specific post [Optional]
5. `TWITTER_POST_DELETE_BY_POST_ID` - Delete a post [Optional]

**Key parameters**:
- `text`: Post text content (max 280 weighted characters)
- `media__media_ids`: Array of media ID strings for attachments
- `reply__in_reply_to_tweet_id`: Tweet ID to reply to
- `quote_tweet_id`: Tweet ID to quote
- `id`: Post ID for lookup/delete

**Pitfalls**:
- Post text is limited to 280 weighted characters; some characters count as more than one
- Posting is NOT idempotent; retrying on timeout will create duplicate posts
- Media IDs must be numeric strings, not integers
- UPLOAD_LARGE_MEDIA is for videos/GIFs; UPLOAD_MEDIA for images
- Always call USER_LOOKUP_ME first to get the authenticated user's ID

### 2. Search Posts

**When to use**: User wants to find tweets matching specific criteria

**Tool sequence**:
1. `TWITTER_RECENT_SEARCH` - Search recent tweets (last 7 days) [Required]
2. `TWITTER_FULL_ARCHIVE_SEARCH` - Search full archive (Academic access) [Optional]
3. `TWITTER_RECENT_SEARCH_COUNTS` - Get tweet count matching query [Optional]

**Key parameters**:
- `query`: Search query using Twitter search operators
- `max_results`: Results per page (10-100)
- `next_token`: Pagination token
- `start_time`/`end_time`: ISO 8601 time range
- `tweet__fields`: Comma-separated fields to include
- `expansions`: Related objects to expand

**Pitfalls**:
- RECENT_SEARCH covers only the last 7 days; use FULL_ARCHIVE_SEARCH for older tweets
- FULL_ARCHIVE_SEARCH requires Academic Research or Enterprise access
- Query operators: `from:username`, `to:username`, `is:retweet`, `has:media`, `-is:retweet`
- Empty results return `meta.result_count: 0` with no `data` field
- Rate limits vary by endpoint and access level; check response headers

### 3. Look Up Users

**When to use**: User wants to find or inspect Twitter user profiles

**Tool sequence**:
1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user [Optional]
2. `TWITTER_USER_LOOKUP_BY_USERNAME` - Look up by username [Optional]
3. `TWITTER_USER_LOOKUP_BY_ID` - Look up by user ID [Optional]
4. `TWITTER_USER_LOOKUP_BY_IDS` - Batch look up multiple users [Optional]

**Key parameters**:
- `username`: Twitter handle without @ prefix
- `id`: Numeric user ID string
- `ids`: Comma-separated user IDs for batch lookup
- `user__fields`: Fields to return (description, public_metrics, etc.)

**Pitfalls**:
- Usernames are case-insensitive but must not include the @ prefix
- User IDs are numeric strings, not integers
- Suspended or deleted accounts return errors, not empty results
- LOOKUP_BY_IDS accepts max 100 IDs per request

### 4. Manage Bookmarks

**When to use**: User wants to save, view, or remove bookmarked tweets

**Tool sequence**:
1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user ID [Prerequisite]
2. `TWITTER_BOOKMARKS_BY_USER` - List bookmarked posts [Required]
3. `TWITTER_ADD_POST_TO_BOOKMARKS` - Bookmark a post [Optional]
4. `TWITTER_REMOVE_A_BOOKMARKED_POST` - Remove bookmark [Optional]

**Key parameters**:
- `id`: User ID (from USER_LOOKUP_ME) for listing bookmarks
- `tweet_id`: Tweet ID to bookmark or unbookmark
- `max_results`: Results per page
- `pagination_token`: Token for next page

**Pitfalls**:
- Bookmarks require the authenticated user's ID, not username
- Bookmarks are private; only the authenticated user can see their own
- Pagination uses `pagination_token`, not `next_token`

### 5. Manage Lists

**When to use**: User wants to view or manage Twitter lists

**Tool sequence**:
1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user ID [Prerequisite]
2. `TWITTER_GET_A_USER_S_OWNED_LISTS` - List owned lists [Optional]
3. `TWITTER_GET_A_USER_S_LIST_MEMBERSHIPS` - List memberships [Optional]
4. `TWITTER_GET_A_USER_S_PINNED_LISTS` - Get pinned lists [Optional]
5. `TWITTER_GET_USER_S_FOLLOWED_LISTS` - Get followed lists [Optional]
6. `TWITTER_LIST_LOOKUP_BY_LIST_ID` - Get list details [Optional]

**Key parameters**:
- `id`: User ID for listing owned/member/followed lists
- `list_id`: List ID for specific list lookup
- `max_results`: Results per page (1-100)

**Pitfalls**:
- List IDs and User IDs are numeric strings
- Lists endpoints require the user's numeric ID, not username

### 6. Interact with Posts

**When to use**: User wants to like, unlike, or view liked posts

**Tool sequence**:
1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user ID [Prerequisite]
2. `TWITTER_RETURNS_POST_OBJECTS_LIKED_BY_THE_PROVIDED_USER_ID` - Get liked posts [Optional]
3. `TWITTER_UNLIKE_POST` - Unlike a post [Optional]

**Key parameters**:
- `id`: User ID for listing liked posts
- `tweet_id`: Tweet ID to unlike

**Pitfalls**:
- Like/unlike endpoints require user ID from USER_LOOKUP_ME
- Liked posts pagination may be slow for users with many likes

## Common Patterns

### Search Query Syntax

**Operators**:
- `from:username` - Posts by user
- `to:username` - Replies to user
- `@username` - Mentions user
- `#hashtag` - Contains hashtag
- `"exact phrase"` - Exact match
- `has:media` - Contains media
- `has:links` - Contains links
- `is:retweet` / `-is:retweet` - Include/exclude retweets
- `is:reply` / `-is:reply` - Include/exclude replies
- `lang:en` - Language filter

**Combinators**:
- Space for AND
- `OR` for either condition
- `-` prefix for NOT
- Parentheses for grouping

### Media Upload Flow

```
1. Upload media with TWITTER_UPLOAD_MEDIA (images) or TWITTER_UPLOAD_LARGE_MEDIA (video/GIF)
2. Get media_id from response
3. Pass media_id as string in media__media_ids array to TWITTER_CREATION_OF_A_POST
```

## Known Pitfalls

**Character Limits**:
- Standard posts: 280 weighted characters
- Some Unicode characters count as more than 1
- URLs are shortened and count as fixed length (23 characters)

**Rate Limits**:
- Vary significantly by access tier (Free, Basic, Pro, Enterprise)
- Free tier: very limited (e.g., 1,500 posts/month)
- Check `x-rate-limit-remaining` header in responses

**Idempotency**:
- Post creation is NOT idempotent; duplicate posts will be created on retry
- Implement deduplication logic for automated posting

## Quick Reference

| Task | Tool Slug | Key Params |
|------|-----------|------------|
| Create post | TWITTER_CREATION_OF_A_POST | text |
| Delete post | TWITTER_POST_DELETE_BY_POST_ID | id |
| Look up post | TWITTER_POST_LOOKUP_BY_POST_ID | id |
| Recent search | TWITTER_RECENT_SEARCH | query |
| Archive search | TWITTER_FULL_ARCHIVE_SEARCH | query |
| Search counts | TWITTER_RECENT_SEARCH_COUNTS | query |
| My profile | TWITTER_USER_LOOKUP_ME | (none) |
| User by name | TWITTER_USER_LOOKUP_BY_USERNAME | username |
| User by ID | TWITTER_USER_LOOKUP_BY_ID | id |
| Users by IDs | TWITTER_USER_LOOKUP_BY_IDS | ids |
| Upload media | TWITTER_UPLOAD_MEDIA | media |
| Upload video | TWITTER_UPLOAD_LARGE_MEDIA | media |
| List bookmarks | TWITTER_BOOKMARKS_BY_USER | id |
| Add bookmark | TWITTER_ADD_POST_TO_BOOKMARKS | tweet_id |
| Remove bookmark | TWITTER_REMOVE_A_BOOKMARKED_POST | tweet_id |
| Unlike post | TWITTER_UNLIKE_POST | tweet_id |
| Liked posts | TWITTER_RETURNS_POST_OBJECTS_LIKED_BY_THE_PROVIDED_USER_ID | id |
| Owned lists | TWITTER_GET_A_USER_S_OWNED_LISTS | id |
| List memberships | TWITTER_GET_A_USER_S_LIST_MEMBERSHIPS | id |
| Pinned lists | TWITTER_GET_A_USER_S_PINNED_LISTS | id |
| Followed lists | TWITTER_GET_USER_S_FOLLOWED_LISTS | id |
| List details | TWITTER_LIST_LOOKUP_BY_LIST_ID | list_id |

---
*Powered by [Composio](https://composio.dev)*

Overview

This skill automates Twitter/X tasks via Rube MCP using Composio's Twitter toolkit. It provides end-to-end flows for posting, searching, user lookups, bookmarks, lists, media uploads, and basic interactions. Designed for agent-driven automation where the MCP exposes current tool schemas.

How this skill works

The skill first queries RUBE_SEARCH_TOOLS to discover the live tool schemas, then manages an authenticated Twitter connection through RUBE_MANAGE_CONNECTIONS. Core workflows call the appropriate MCP tool sequence (e.g., USER_LOOKUP_ME, UPLOAD_MEDIA, CREATION_OF_A_POST) and handle required parameters like numeric-string IDs, media_ids arrays, and search queries. It enforces the pattern of confirming ACTIVE connection and using the authenticated user ID for user-scoped endpoints.

When to use it

  • Create, reply to, quote, or delete tweets and attach images or video
  • Search recent or archived tweets with advanced query operators
  • Inspect or batch-look up user profiles by username or numeric ID
  • Save, list, or remove private bookmarks for the authenticated user
  • Manage and inspect user-owned, followed, or pinned Twitter lists
  • List or unlike posts liked by the authenticated user

Best practices

  • Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas before invoking endpoints
  • Call TWITTER_USER_LOOKUP_ME to get the authenticated user ID before user-scoped operations
  • Use TWITTER_UPLOAD_LARGE_MEDIA for video/GIF and TWITTER_UPLOAD_MEDIA for images; pass media IDs as numeric strings in an array
  • Treat post creation as non-idempotent; implement deduplication or client-side idempotency checks
  • Respect rate limits: read x-rate-limit-* headers and back off or paginate using next_token/pagination_token

Example use cases

  • Automatically post a scheduled tweet with image attachments via UPLOAD_MEDIA + CREATION_OF_A_POST
  • Build a search-based monitor that uses RECENT_SEARCH and RECENT_SEARCH_COUNTS to surface trending mentions
  • Bulk-inspect a list of influencers using USER_LOOKUP_BY_IDS to collect public_metrics
  • Create a bookmark manager that lists bookmarks and toggles them with ADD_POST_TO_BOOKMARKS / REMOVE_A_BOOKMARKED_POST
  • Archive a list of tweets matching a complex query using FULL_ARCHIVE_SEARCH (requires proper access)

FAQ

Do I need API keys to use Rube MCP?

No API keys are required for the MCP endpoint; add https://rube.app/mcp to your client configuration and use the provided MCP actions.

What if I get empty search results?

Empty results return meta.result_count: 0 with no data field. Confirm your query syntax, time range, and access tier (RECENT_SEARCH covers only the last 7 days).

How should I handle media IDs and user IDs?

Always pass media IDs and user IDs as numeric strings, never integers. Retrieve the authenticated user ID via USER_LOOKUP_ME before user-scoped calls.