Twitter Comment Collection

Submit one Twitter post for public comment collection and retrieve structured comment records when the task is ready.

原文 · en-US訳文に戻す

データ収集 Social Media X (Twitter)Reviews & Ratings

開発者

hello_moto

料金

$0.002 / 11 件から

最終更新

2026-10-12

概要

Collect public replies to one Twitter post as structured records for social listening, community analysis, and content research. Submit a post ID with the desired comment count, then receive each available comment together with author, timing, media, source-post, and engagement context.

Data notes

Each row represents one comment returned for the submitted public Twitter post. Comment ID and Source post ID preserve the relationship between the reply and the post being monitored. Author fields, text, URLs, media references, timestamps, and engagement counts are retained when supplied by the source. Comment videos and image URLs are returned as JSON-encoded text when available. Count fields are source-provided text values, and collection or publish timestamps may not include an explicit timezone.

The collection covers public, discoverable Twitter comments only. Private, deleted, inaccessible, or otherwise unavailable comments are not covered. Empty or unavailable collection items may be represented by the No-data marker and task metadata.

What a result looks like

Each row is one collected Twitter comment.

Comment ID	Comment text	Comment author handle	Publish time	Like count	No-data marker
2102029309472805246	@YozoraWolf @RVyolie @KeitaroTR I already had over 1.4k Gear Artificing Catalyst, so I wasn't worried about losing one or two week worth of shop material.	Yukikaze______	2026-09-21T21:36:55	2	No

Source post ID, author ID, comment URL, media references, reply count, share count, view count, collection time, task item, and other source fields are also available when supplied.

Use cases

For community research, group rows by Comment author handle and inspect Comment text to identify recurring participants and themes.
For moderation or support analysis, filter Comment text and Comment URL to review public replies associated with a post.
For engagement analysis, compare Like count, Reply count, Share count, and View count alongside Publish time.

適用範囲と境界

One public Twitter post per task with a requested comment count; results are returned as comment records through asynchronous task processing and paginated retrieval.

適している用途
When you need structured public comments for a Twitter post, including comment text, author identifiers, timestamps, media references, and engagement counts.
When you need to monitor replies to a public post and retain the source post context beside each comment.

適さない用途
When you need private, deleted, or non-public Twitter comments.
When you need an immediate single-comment lookup rather than an asynchronous collection task.

失敗時の処理

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

1If the task expires or fails, submit the same post again and use the new task identifier.
2If no data is returned, verify that the post is public and has discoverable comments.
3Retry later after authentication failures, rate limits, temporary unavailability, or timeouts.

入力

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

Twitter post IDpost_id必須string
The ID of one public Twitter post whose comments should be collected. The upstream accepts up to 512 characters.
例2102028592125473050
Requested comment countcomments_spider_num必須integer
The number of comments to request for the post. The upstream documentation does not specify a maximum; provide the desired count explicitly.
例10

出力

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

Business IDbiz_idstring
Business grouping identifier associated with the source post.
例2102028592125473050
Comment IDcomment_idstring
Unique identifier of the collected Twitter comment.
例2102029309472805246
Comment textcomment_textstring
Text content of the collected comment, including mentions, line breaks, and links when supplied.
例@YozoraWolf @RVyolie @KeitaroTR I already had over 1.4k Gear Artificing Catalyst, so I wasn't worried about losing one or two week worth of shop material. All I can say is that the experience may come with quite some frustrating moment, but feels rewarding in the end. It felt worth it to me
Comment timecomment_timestring
Source-provided display time associated with the comment; the source format includes a UTC offset.
例Mon Sep 21 13:36:55 +0000 2026

サンプルデータ

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

output.example

{
  "biz_id": "2102028592125473050",
  "comment_id": "2102029309472805246",
  "comment_text": "@YozoraWolf @RVyolie @KeitaroTR I already had over 1.4k Gear Artificing Catalyst, so I wasn't worried about losing one or two week worth of shop material.\n\nAll I can say is that the experience may come with quite some frustrating moment, but feels rewarding in the end. It felt worth it to me",
  "comment_time": "Mon Sep 21 13:36:55 +0000 2026",
  "comment_type": "1",
  "comment_url": "https://twitter.com/Yukikaze______/status/2102029309472805246",
  "comment_user_avatar_url": "https://pbs.twimg.com/profile_images/2071806778090700801/bq6bQl6I_normal.jpg",
  "comment_user_display_id": "Yukikaze______",
  "comment_user_id": "1890315900949262338",
  "comment_user_name": "Yukikaze",
  "comment_videos": "[\"https://pbs.twimg.com/amplify_video_thumb/2097006050184749056/img/pVUa7PlCNZTedjQU.jpg\"]",
  "content_id": "2102028592125473050",
  "crawl_time": "2026-09-22T10:33:51",
  "image_urls": "[]",
  "keyword": "2102028592125473050",
  "like_count": "2",
  "parent_comment_id": "2102029309472805246",
  "publish_time": "2026-09-21T21:36:55",
  "reply_count": "1",
  "share_count": "0",
  "view_count": "9",
  "task_item": "2102028592125473050",
  "no_data": false
}

連携方法

この 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=hello_moto/twitter-comment",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

自分の API Keys を表示 →

AI に設定を任せる

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

detail.access.mcp.composeHint

料金

per accepted task

返される件数にかかわらず、実行の送信 1 回ごとに課金されます。

$0.001/ 回

per returned 11 comment

正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。 11 件を 1 つの課金単位とし、端数は 11 件に切り上げて課金されます。

$0.002/ 11 件

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

Credits を確認

今すぐ試す

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

サンプル

パラメータは送信前に input.schema で検証されます

Twitter post IDpost_id*The ID of one public Twitter post whose comments should be collected. The upstream accepts up to 512 characters.

Requested comment countcomments_spider_num*The number of comments to request for the post. The upstream documentation does not specify a maximum; provide the desired count explicitly.