X/Twitter Keyword & Hashtag Tweet Search: MCP config, n8n workflow and API

{
  "keywords": [
    "apify"
  ],
  "maxTweets": 20,
  "searchType": "Latest",
  "language": "Any language",
  "excludeRetweets": false,
  "excludeReplies": false,
  "onlyVerifiedUsers": false,
  "onlyImages": false,
  "onlyVideos": false,
  "onlyQuotes": false,
  "matchMode": "all",
  "onlyNew": false,
  "monitoringEnabled": false
}

---
name: x-twitter-keyword-and-hashtag-tweet-search
description: "Tweets found for your keywords — text, author, engagement metrics, media and the search term that found each row. Runs the Apify Actor nimbryxo-studio/x-twitter-keyword-and-hashtag-tweet-search. Use when the user needs X (Twitter) data with fields such as type, searchTerm, text, author.username, createdAt, language and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/x-twitter-keyword-and-hashtag-tweet-search"
  store-url: "https://apify.com/nimbryxo-studio/x-twitter-keyword-and-hashtag-tweet-search"
---

# X/Twitter Keyword & Hashtag Tweet Search

Use this skill to fetch X (Twitter) data with the Apify Actor `nimbryxo-studio/x-twitter-keyword-and-hashtag-tweet-search` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `keywords` | array, required | Words, phrases, hashtags or full X search queries to monitor. Each keyword is searched separately, and every result row tells you which keyword found it (searchTerm). |
| `maxTweets` | integer | Stop after this many tweets for each keyword. This is a target, not a guarantee: guest X search returns ~20 posts per answered page, the Phase 6 probes measured 300 unique rows for a 300-row target, and 500/1,000 are unverified. |
| `searchType` | one of `Top`, `Latest` | Latest returns the newest posts first. Top is engagement-ranked output: X's logged-out search never serves the real Top timeline, so the actor collects Latest pages and sorts them by like count client-side. |
| `language` | string | Only return tweets written in this language. Leave the default to search all languages. |
| `excludeRetweets` | boolean | Skip retweets/reposts and keep only original posts. |
| `excludeReplies` | boolean | Skip replies and keep only top-level posts. |
| `onlyVerifiedUsers` | boolean | Only return tweets from verified (blue check) accounts. |
| `onlyImages` | boolean | Only return tweets that contain at least one image. |
| `onlyVideos` | boolean | Only return tweets that contain at least one video or GIF. |
| `onlyQuotes` | boolean | Only return quote tweets (filter:quote). |
| `matchMode` | one of `all`, `any`, `exact` | How to combine the words in each keyword: all = X's default AND, any = (word1 OR word2), exact = quoted phrase. |
| `onlyNew` | boolean | Return only posts newer than the previous run for this keyword. The actor stores a numeric tweet-id watermark plus an overlap window in the key-value store, so scheduled runs do not repeat old rows. |
| `monitoringEnabled` | boolean | Alias that enables onlyNew when onlyNew itself is not provided. Prefer the Only new posts field. |

Example `input.json` (the Actor's published prefill):

```json
{
  "keywords": [
    "apify"
  ],
  "maxTweets": 20,
  "searchType": "Latest",
  "language": "Any language",
  "excludeRetweets": false,
  "excludeReplies": false,
  "onlyVerifiedUsers": false,
  "onlyImages": false,
  "onlyVideos": false,
  "onlyQuotes": false,
  "matchMode": "all",
  "onlyNew": false,
  "monitoringEnabled": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~x-twitter-keyword-and-hashtag-tweet-search/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~x-twitter-keyword-and-hashtag-tweet-search/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `type`, `searchTerm`, `text`, `author.username`, `createdAt`, `language`, `replyCount`, `retweetCount`, `likeCount`, `quoteCount`, `viewCount`, `engagementRate`, `isRetweet`, `isQuote`, `isReply`, `url`, `media`, `collectedAt`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.