Search X tweets
Input
query requiredRaw X search query. Supports all X search operators, e.g. '"AI automation" min_faves:500 since:2026-06-04'. Combining -filter:replies with min_faves and since can unexpectedly return zero results; using fewer operators together is more reliable. The query is taken literally, so if it targets a person or organization ambiguously — a bare first name, a nickname, or a handle you are not certain is exact, meant for from:/to:/@ targeting — resolve the exact handle first (for example via get_user_info, or by asking) rather than guessing: a wrong guess does not error, it silently searches the wrong thing and returns a plausible-looking but incorrect result set.
tab optionalWhich search tab: 'top' (ranked, default) or 'latest' (chronological). Top is a sample, not an exhaustive ranking.
Default: "top"count optionalMax tweets to return. The script scrolls until count is met or results dry up. Default 20, max 100.
Default: 20Output
count requiredNumber of tweets returned. 0 is a first-class outcome (no results for the query).
query requiredtweets requiredFAQ
Delete tweet
Delete one of your own tweets given its URL. Returns the deleted tweet id and a deleted flag.
Get X user posts
Get a user's Posts tab by handle (x.com/<handle>) — their own tweets and self-threads, newest first. Excludes replies to others (see get_user_replies for the Replies tab), and excludes reposts, which X keeps on a separate Reposts tab. The post count shown on the profile header includes replies, so expect fewer items than that number. Returns per tweet: id, url, text, created_at, lang, likes, retweets, replies, quotes, views, bookmarks, is_retweet, is_quote. Count is capped by how far X paginates before throttling.
Get X tweet
Fetch a tweet by URL — the focal post plus the surrounding conversation. Returns `tweet` (the focal post; null if deleted/tombstoned) and `replies[]`, which holds every other tweet on the conversation page: both the focal's ancestors (the thread above it, present when the focal is itself a reply; each has `in_reply_to` null or pointing above the focal) and the replies below it (`in_reply_to` points at the focal or a sibling reply). Use `in_reply_to` to tell ancestors from replies and rebuild the thread — the array is not filtered to descendants of the focal. Each entry is a canonical tweet record: id, url, author {id, handle, name}, text, created_at, lang, likes, retweets, replies, quotes, bookmarks, views, is_retweet, is_quote, in_reply_to {id, author_handle}. Scrolls the main thread until `count` is met (then complete=false — more may exist) or it drains (complete=true). Replies behind a "Show more replies"/hidden/probable-spam cursor are not expanded, so even complete=true is a floor, not a guarantee every nested reply was seen.