1本のBilibili動画のBV IDまたはav IDを指定して、公開コメント、ユーザー情報、反応指標、タイムスタンプを収集します
YouTube Video Comments
Give one YouTube video link and an expected comment count to receive public comments, authors, engagement, and publish times
原文 · en-US訳文に戻す
概要
Public comments on a YouTube video show how viewers react in their own words, which remarks attract replies, and whether the creator engages back. This Data App turns the public comment area of one video into a consistent dataset with comment text, author details, reply relationships, engagement snapshots, and timestamps.
The result is suited to repeatable analysis rather than manual scrolling. It keeps the original comment wording and connects each comment to its video, author, and parent comment, making it easier to compare reactions, identify recurring themes, and inspect conversations around a video.
Data notes
The data covers comments that are publicly visible on the supplied YouTube video at collection time. Records are ordered from newest to oldest by Published at. Each normal record is identified by its Comment ID, which is used to remove duplicates. Private, deleted, members-only, and closed-comment videos are outside the coverage.
Like count, Reply count, Dislike count, Comment count, Channel owner, and Creator heart are snapshots and may change after collection. Count values and classification values such as Comment type and Raw comment type are retained as source text rather than converted into numbers. Published at, Collected at, and Cleaned at preserve the source timestamps without inferring a timezone. Relative time keeps the on-page display text, such as 1年前. Keyword, Business ID, Video URL, and Source item may repeat the submitted video link when that is what the source record carries. No data retains the collection outcome when a video has no public comment result.
What the results look like
Each normal record represents one publicly visible comment from the selected YouTube video.
| Comment ID | Comment text | Author ID | Published at | Like count | Reply count |
|---|---|---|---|---|---|
| UgwnKwe6YJKooQl-JaZ4AaABAg | 年紀漸長覺得這好像不錯 可以有大按鈕也不用佔螢幕空間 | @attacksoil | 2025-08-25T14:52:01 | 1 | 0 |
| UgwYMOjMzFk7w-8L0Fl4AaABAg | Good job DR RICK 👍 | @JoeGentry-g7k | 2025-08-27T15:03:26 | 0 | 0 |
Additional values include avatar and channel details, video identifiers, reply relationships, creator interaction flags, collection timestamps, and the no-data outcome.
Use cases
- Compare Comment text with Like count and Reply count to identify remarks that generated stronger visible engagement.
- Group Comment text by recurring phrases, then use Published at to see how the discussion changed over time.
- Reconstruct reply threads with Parent comment ID and Comment type to distinguish top-level remarks from follow-up replies.
- Review Channel owner and Creator heart together with Author ID to see how the channel participated in the discussion.
適用範囲と境界
Each run collects comments from one YouTube video. The expected comment count is 1 to 10000. Results are returned in complete batches of 20, so the actual count may be rounded up. Only publicly visible comments at collection time are covered.
- 適している用途
- When you need public comment text and engagement details from a specific YouTube video
- When you need comment authors, reply relationships, timestamps, and creator interaction signals for analysis
- 適さない用途
- When you need comments from more than one video in a single run — submit a separate run for each video
- When you need private, deleted, members-only, or closed-comment data — this App covers publicly visible comments only
失敗時の処理
開発者が宣言した失敗時と再試行の動作です。連携時にはシステムプロンプトに含めることをおすすめします。
- 1If no comments are returned, verify the video link and confirm that the video and its comments are publicly visible
- 2Retry later after rate limiting, temporary service unavailability, or a timeout
- 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
- 4If authentication fails, verify the API Key configured for the execution environment
入力
この App の呼び出しに必要なパラメータで、manifest.json の input.schema から生成されています。
- Video link
video_url必須stringThe full YouTube watch URL of the public video whose comments will be collected. Enter one video link only; an invalid or inaccessible video may return no comments.例https://www.youtube.com/watch?v=mpUwmWy_tlg - Expected comment count
comment_count必須integerThe expected number of comments to collect, from 1 to 10000. Results are returned and billed in complete batches of 20, so the actual count may be rounded up.範囲1–10000例20
出力
1 件のレコードのフィールド構造で、manifest.json の output.schema から生成されています。
- Comment ID
comment_idstringThe stable unique identifier of the YouTube comment例UgwnKwe6YJKooQl-JaZ4AaABAg - Video ID
content_idstringThe identifier of the YouTube video associated with the comment例mpUwmWy_tlg - Record ID
cur_idstringThe source record identifier returned with this comment例6a8d3b9297884a4f18a27756 - Comment type
comment_typestringThe source value identifying the comment type, retained as source text例1
サンプルデータ
output.schema から生成したサンプルです。サンプル値のないフィールドには構造上のプレースホルダーを使用しています。
{
"comment_id": "UgwnKwe6YJKooQl-JaZ4AaABAg",
"content_id": "mpUwmWy_tlg",
"cur_id": "6a8d3b9297884a4f18a27756",
"comment_type": "1",
"parent_comment_id": "<parent_comment_id>",
"comment_user_id": "@attacksoil",
"comment_user_avatar_url": "https://yt3.ggpht.com/ytc/AIdro_nx14vEi8CIGWe-1TfJUlTVRCSMosevvM0iyj2yylc=s88-c-k-c0x00ffffff-no-rj",
"comment_text": "年紀漸長覺得這好像不錯 可以有大按鈕也不用佔螢幕空間",
"publish_time": "2025-08-25T14:52:01",
"crawl_time": "2026-08-25T14:52:02",
"like_count": "1",
"reply_count": "0",
"keyword": "https://www.youtube.com/watch?v=mpUwmWy_tlg",
"root_content_url": "https://www.youtube.com/watch?v=mpUwmWy_tlg",
"channel_name": "<channel_name>",
"comment_time": "1年前",
"raw_comment_type": "0",
"dislike_count": "<dislike_count>",
"clean_update_time": "2026-08-25T14:52:02",
"author_is_channel_owner": false,
"comment_count": "4",
"has_creator_heart": false,
"biz_id": "https://www.youtube.com/watch?v=mpUwmWy_tlg",
"source_item": "https://www.youtube.com/watch?v=mpUwmWy_tlg",
"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": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/youtube-video-comments",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}AI に設定を任せる
設定を手作業で編集したくない場合は、インストールプロンプトをコピーして任意の AI クライアントに貼り付けてください。AI が自分のやり方でセットアップを完了します(デフォルトではログインを案内し、API Key をチャットに送るよう求めることはありません)。
detail.access.mcp.composeHint
料金
正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。 20 件を 1 つの課金単位とし、端数は 20 件に切り上げて課金されます。
返される件数にかかわらず、実行の送信 1 回ごとに課金されます。
複数の課金イベントはそれぞれ独立して累計されます。詳細は各項目をご覧ください。失敗した実行には課金されません。
Credits を確認今すぐ試す
パラメータを入力して実行してください。結果は実際の呼び出しによるものです。