EN

YouTube Video Comments

Give one YouTube video link and an expected comment count to receive public comments, authors, engagement, and publish times

Developer
Pricing
From $0.002 / 20 records
Last updated
2026-09-18

Overview

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 IDComment textAuthor IDPublished atLike countReply count
UgwnKwe6YJKooQl-JaZ4AaABAg年紀漸長覺得這好像不錯 可以有大按鈕也不用佔螢幕空間@attacksoil2025-08-25T14:52:0110
UgwYMOjMzFk7w-8L0Fl4AaABAgGood job DR RICK 👍@JoeGentry-g7k2025-08-27T15:03:2600

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.

Scope and boundaries

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.

  • Good for
  • 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
  • Do not use for
  • 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

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

  1. 1If no comments are returned, verify the video link and confirm that the video and its comments are publicly visible
  2. 2Retry later after rate limiting, temporary service unavailability, or a timeout
  3. 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
  4. 4If authentication fails, verify the API Key configured for the execution environment

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

  • Video linkvideo_urlRequiredstring
    The 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.
    Examplehttps://www.youtube.com/watch?v=mpUwmWy_tlg
  • Expected comment countcomment_countRequiredinteger
    The 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.
    Range1–10000Example20

Output

Field structure of a single record, generated from the output.schema in manifest.json.

  • Comment IDcomment_idstring
    The stable unique identifier of the YouTube comment
    ExampleUgwnKwe6YJKooQl-JaZ4AaABAg
  • Video IDcontent_idstring
    The identifier of the YouTube video associated with the comment
    ExamplempUwmWy_tlg
  • Record IDcur_idstring
    The source record identifier returned with this comment
    Example6a8d3b9297884a4f18a27756
  • Comment typecomment_typestring
    The source value identifying the comment type, retained as source text
    Example1

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example
{
  "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
}

Integration

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=hello_moto/youtube-video-comments",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)

detail.access.mcp.composeHint

Pricing

20 returned comments

Charged by the number of records successfully returned. Failed runs are not charged. Billed in units of 20 records; any partial unit is rounded up to 20 records.

$0.002/ 20 records
Per task submitted

Charged once per submitted run, regardless of how many records are returned.

$0.0001/ run

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
From $0.002 / 20 records