logo
JP

Twitter Hashtag Post Scraper

Collect public Twitter posts for up to three keywords or hashtags, including authors, content, media links, timestamps, and engagement metrics.

開発者
YiJacobJohnRaku
料金
$0.0003 / 件
最終更新
2026-09-10

概要

Twitter Hashtag Post Scraper turns a small set of keywords or hashtags into structured public-post records that are ready to filter, compare, and analyze. Each record keeps the matched term, search-result category, post and author links, author name, publication time, post text, media links, advertising indicator, and reported engagement counts.

This dataset helps teams move from scattered social posts to a consistent evidence table. It preserves the text and the surrounding context needed to compare conversations, identify visible authors, inspect recurring themes, and understand which collected posts attracted more engagement at the time of collection.

Data notes

Records come from publicly visible Twitter search results and reflect what the collector could access when the run took place. A record represents one collected post associated with one submitted term and search-result category. The same post address is used to remove duplicates across retrieved result pages. Post timestamps retain the source's displayed UTC offset. Reply, retweet, like, and view counts are snapshots reported at collection time and can change afterward; they are preserved as reported text rather than recalculated values. Image links may point to an image or a video thumbnail, and a reported video link may be the same as the post link. Private, deleted, restricted, and sign-in-only content is not covered.

What the results look like

Each record is one collected public post:

Author namePost contentPost timestampPost URLLike countView count
Republicans against TrumpFlashback — Donald Trump: “If Ivanka weren’t my daughter, perhaps I’d be dating her” — TV host: “Stop it. It's so weird.” #TrumpIsWeird #TBT https://t.co/JOXOCp27CpFri Aug 02 02:17:50 +0000 2024https://x.com/RpsAgainstTrump/status/1819195875580629097333715879786
OgilvyHow to Write – A memo drafted by David Ogilvy on September 7, 1982, for the management to circulate as they saw fit. #TBTThu Sep 03 13:00:20 +0000 2026https://x.com/Ogilvy/status/209549712014066533332713270

The output also includes “Matched term,” “Result category,” “Search page URL,” “Author profile URL,” “Image URL,” “Video URL,” “Ad indicator,” “Reply count,” and “Retweet count.”

Use cases

  • For hashtag conversation research, group records by “Matched term” and review “Post content” to identify recurring topics, claims, and phrases.
  • For visible-author discovery, compare “Author name” and “Author profile URL,” then use “Post URL” to inspect the original public context.
  • For engagement comparisons, evaluate “Reply count,” “Retweet count,” “Like count,” and “View count” together instead of treating one interaction measure as the whole response.
  • For content-format analysis, compare “Image URL,” “Video URL,” and “Post content” to see which collected posts pair text with reported media.

適用範囲と境界

Each run accepts 1 to 3 keywords or hashtags and up to 200 scroll-downs; retrieval is capped at 10,000 public post records per run.

  • 適している用途
  • Use it when you need a structured snapshot of public Twitter posts associated with a small set of keywords or hashtags.
  • Use it for hashtag monitoring, content research, author discovery, or engagement comparisons.
  • 適さない用途
  • Do not use it for private, deleted, restricted, or sign-in-only posts because only content visible to the collector is covered.
  • Do not use it when complete historical coverage or a guaranteed post count is required because availability can change over time.

失敗時の処理

開発者が宣言した失敗時と再試行の動作です。連携時にはシステムプロンプトに含めることをおすすめします。

  1. 1If a run stops before completion, retry the same small input once; if it stops again, use fewer terms or a smaller scroll-down value.
  2. 2An empty result can mean the term has no visible matching posts or access was temporarily limited; verify the spelling and retry later.

入力

この App の呼び出しに必要なパラメータで、manifest.json の input.schema から生成されています。

  • Keywords or hashtagsquery_terms必須array<string>
    Keywords or hashtags to search on Twitter, with one term per item. Enter 1 to 3 terms per run.
    件数最大 3 件例["#tbt"]
  • Scroll-down countscroll_down_times任意integer
    How many times to load more search results, from 1 to 200. When omitted, the collector decides the depth; set it explicitly when a predictable depth is important.
    範囲1–200

出力

1 件のレコードのフィールド構造で、manifest.json の output.schema から生成されています。

  • Result categorycategorystring
    Search-result grouping reported for the post, such as TopPost.
    例TopPost
  • Matched termkeywordstring
    Keyword or hashtag associated with the collected post.
    例#tbt
  • Search page URLsearch_page_urlstring
    Twitter search address from which the post was collected.
    例https://twitter.com/search?q=#tbt&src=typed_query&f=top
  • Post URLtweet_urlstring
    Direct address of the collected Twitter post.
    例https://x.com/RpsAgainstTrump/status/1819195875580629097

サンプルデータ

output.schema から生成したサンプルです。サンプル値のないフィールドには構造上のプレースホルダーを使用しています。

output.example
{
  "category": "TopPost",
  "keyword": "#tbt",
  "search_page_url": "https://twitter.com/search?q=#tbt&src=typed_query&f=top",
  "tweet_url": "https://x.com/RpsAgainstTrump/status/1819195875580629097",
  "author_name": "Republicans against Trump",
  "author_profile_url": "https://x.com/RpsAgainstTrump",
  "tweet_timestamp": "Fri Aug 02 02:17:50 +0000 2024",
  "tweet_content": "Flashback \n\nDonald Trump: “If Ivanka weren’t my daughter, perhaps I’d be dating her”\n\nTV host: “Stop it. It's so weird.” #TrumpIsWeird #TBT https://t.co/JOXOCp27Cp",
  "image_url": "https://pbs.twimg.com/amplify_video_thumb/1819195812393406464/img/KAyMW9OE6elaK1HB.jpg",
  "video_url": "https://x.com/RpsAgainstTrump/status/1819195875580629097",
  "ad_indicator": "False",
  "reply_count": "2818",
  "retweet_count": "10855",
  "like_count": "33371",
  "view_count": "5879786"
}

連携方法

この App は MCP、API、SDK、ファイルエクスポートのいずれでも連携でき、どのチャネルも同じ能力と料金を共有します。すべてのリクエストは Authorization: Bearer ヘッダーで認証し、認証情報には API Key(長期有効。Data Hub コンソールで作成)を使用します。MCP クライアントは OAuth によるキー不要のログインにも対応しています。CLI や Skill など、さらに多くの連携方法も準備中です。 この App は非同期で実行され、途中でキャンセルできます:キャンセル後、実行は停止します。納品済みのレコードは保持され、課金対象になります。

MCP(Model Context Protocol)を使うと、Claude や Cursor などの AI クライアントからこの App を直接呼び出せます。クライアントと認証方式を選び、下の設定をコピーしてください。

クライアント設定

Bearer の後の値を長期有効な API Key に置き換えてください。あらゆるクライアント、CI、ヘッドレス環境で利用できます。

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=YiJacobJohnRaku/twitter-scraper-by-hashtag",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

AI に設定を任せる

設定を手作業で編集したくない場合は、インストールプロンプトをコピーして任意の AI クライアントに貼り付けてください。AI が自分のやり方でセットアップを完了します(プロンプトは AI があなたに API Key を尋ねる形になっているため、認証情報がチャット履歴や共有設定に残りません)。

detail.access.mcp.composeHint

料金

returned post record

正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。

$0.0003/ 件

複数の課金イベントはそれぞれ独立して累計されます。詳細は各項目をご覧ください。失敗した実行には課金されません。

Credits を確認

今すぐ試す

パラメータを入力して実行してください。結果は実際の呼び出しによるものです。

サンプル
パラメータは送信前に input.schema で検証されます
$0.0003 / 件