logo
JP

Twitter (X) Comments Scraper

Collect public replies from Twitter post URLs with the source post, reply author, content, timestamps, media links, and engagement details.

データ収集Social MediaX (Twitter)Posts
開発者
YiJacobJohnRaku
料金
$0.0003 / 件
最終更新
2026-09-10

概要

Twitter (X) Comments Scraper turns known public post URLs into structured reply records that are ready to review, filter, and compare. Each record connects one reply to its source post and preserves the post and reply links, authors, text, publication times, media links, visible engagement counts, deletion indicator, and any collection message.

This dataset helps teams move beyond a post-level engagement total and inspect the conversation underneath it. Because each reply stays linked to the source post and the replying account, the results can support qualitative conversation review, visible-audience research, response-pattern analysis, and evidence gathering around a defined set of posts.

Data notes

Records come from publicly accessible Twitter conversations and reflect what the collector could see when the run took place. Each record represents one collected reply to one submitted source post, and the reply URL is used to remove duplicate records across retrieved result pages. Post and reply timestamps retain the source's displayed UTC offset. Like, retweet, reply, bookmark, and view counts are snapshots reported at collection time and can change afterward; they are preserved as reported text rather than recalculated values. Multiple source-post image addresses may be joined with vertical bars, while an empty reply-image value means no image was reported for that reply. Private, restricted, deleted, and sign-in-only content may not be available.

What the results look like

Each record is one collected public reply linked to its source post:

Reply author nameReply contentReply timestampReply URLReply likesReply views
ALT_uscis@smutoro @Meta @instagram @facebook The COVID era was THE TRUMP ERA YOU MORONTue Aug 27 13:49:59 +0000 2024https://x.com/ALT_uscis/status/182842975610829645213713
ExampleResponderA short public response to the source post.Tue Aug 27 14:02:10 +0000 2024https://x.com/ExampleResponder/status/18284328000000000004128

The output also includes “Source post URL,” “Source post ID,” “Post author name,” “Post author URL,” “Post timestamp,” “Post content,” “Post image URLs,” “Post likes,” “Post retweets,” “Post replies,” “Post bookmarks,” “Reply author URL,” “Reply image URL,” “Reply retweets,” “Nested replies,” “Deletion indicator,” and “Collection message.”

Use cases

  • For conversation analysis, group records by “Source post URL” and review “Reply content” to identify recurring questions, objections, claims, and themes beneath each post.
  • For visible-audience research, compare “Reply author name” and “Reply author URL,” then use “Reply URL” to inspect the original public context.
  • For reply-engagement comparisons, evaluate “Reply likes,” “Reply retweets,” “Nested replies,” and “Reply views” together to identify which collected responses drew more visible interaction.
  • For post-to-reply context review, compare “Post content” with “Reply content” and their respective timestamps to preserve the relationship between a statement and the responses it received.

適用範囲と境界

Each run accepts 1 to 100,000 public Twitter post URLs and can request up to 100,000 replies per post; retrieval is capped at 10,000 returned records per run.

  • 適している用途
  • Use it when you need reply-level records for one or more known public Twitter posts.
  • Use it for conversation analysis, respondent discovery, reply engagement comparisons, or evidence collection around specific posts.
  • 適さない用途
  • Do not use it to discover posts by keyword or hashtag because it starts from known post URLs.
  • Do not use it for private, deleted, restricted, or sign-in-only conversations because only content visible to the collector is covered.

失敗時の処理

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

  1. 1If a run stops before completion, retry the same small input once; if it stops again, use fewer post URLs or request fewer replies.
  2. 2An empty result can mean the post has no visible replies, the URL is unavailable, or access was temporarily limited; verify the post URL and retry later.

入力

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

  • Twitter post URLstweet_urls必須array<string>
    Public Twitter or X post URLs whose replies should be collected. Enter 1 to 100,000 URLs per run.
    件数最大 100000 件例["https://x.com/smutoro/status/1828297507484438722"]
  • Replies per postreply_limit任意integer
    Maximum number of replies to request for each post, from 1 to 100,000. When omitted, the collector decides the limit; set it explicitly when a predictable depth is important.
    範囲1–100000

出力

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

  • Source post URLtweet_urlstring
    Direct address of the source Twitter post.
    例https://x.com/smutoro/status/1828297507484438722
  • Source post IDtweet_idstring
    Identifier of the source Twitter post.
    例1828297507484438722
  • Post author nametweet_author_namestring
    Display name of the account that published the source post.
    例Stephen Mutoro
  • Post author URLtweet_author_profile_urlstring
    Direct address of the source post author's profile.
    例https://x.com/smutoro

サンプルデータ

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

output.example
{
  "tweet_url": "https://x.com/smutoro/status/1828297507484438722",
  "tweet_id": "1828297507484438722",
  "tweet_author_name": "Stephen Mutoro",
  "tweet_author_profile_url": "https://x.com/smutoro",
  "tweet_posted_at_utc": "Tue Aug 27 05:04:28 +0000 2024",
  "tweet_content": "The @Meta, @instagram and @facebook owner Mark Zuckerberg says he regrets working with the Biden-Harris administration to censure information online during the #Covid19 era https://t.co/G8nKVLDDPG",
  "tweet_image_urls": "https://pbs.twimg.com/ext_tw_video_thumb/1828297475221774336/pu/img/dMCF64ISghcByCeH.jpg|https://pbs.twimg.com/media/GV9q30sWwAAU7cU.jpg|https://pbs.twimg.com/media/GV9q3xVXAAEzT4Y.jpg",
  "tweet_likes": "212",
  "tweet_retweets": "93",
  "tweet_replies": "52",
  "tweet_bookmarks": "89",
  "comment_url": "https://x.com/ALT_uscis/status/1828429756108296452",
  "comment_author_name": "ALT_uscis",
  "comment_author_profile_url": "https://x.com/ALT_uscis",
  "comment_timestamp": "Tue Aug 27 13:49:59 +0000 2024",
  "comment_content": "@smutoro @Meta @instagram @facebook The COVID era was THE TRUMP ERA YOU MORON",
  "comment_image_url": "",
  "comment_likes": "13",
  "comment_retweets": "0",
  "comment_replies": "2",
  "comment_views": "713",
  "is_deleted": "False",
  "error_message": ""
}

連携方法

この 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/tweets-comments-scraper-by-search-result-url",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}
自分の API Keys を表示 →

AI に設定を任せる

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

detail.access.mcp.composeHint

料金

returned comment record

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

$0.0003/ 件

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

Credits を確認

今すぐ試す

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

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