logo
EN

Twitter Comment Replies

Give one Twitter comment ID and an optional reply count to receive public replies with authors, timestamps, links, and engagement metrics.

Data collectionSocial MediaX (Twitter)Reviews & Ratings
Developer
hello_moto
Pricing
From $0.002 / 11 records
Last updated
2026-10-12

Overview

A Twitter conversation often becomes useful only after the replies are connected back to the comment that started them. This app turns one public Twitter comment ID into a structured collection of public replies, keeping the reply text, author, timestamps, links, parent relationship, and engagement context together for analysis.

The result is designed for conversation review rather than manual browsing. It helps preserve the wording of replies and makes it easier to compare participants, reconstruct reply relationships, and identify the public responses associated with a source comment.

Data notes

Each normal record represents one public Twitter reply associated with the submitted comment ID. Reply records are de-duplicated by Reply comment ID. The source returns records in collection-time order and exposes reply counts, page metadata, and a no-data marker when the source explicitly reports that no data is available.

Text, identifiers, URLs, timestamps, and engagement counts are retained as returned by the source. Count fields remain source text, while timestamps preserve their source representation and should not be converted into a different timezone without additional context. Private, deleted, or otherwise unavailable Twitter content is outside the coverage.

What a result looks like

Each row represents one public Twitter reply connected to the submitted comment.

Reply comment IDReply textAuthor namePublished timeLike countParent comment ID
2100351577437663410@sousi526 Good morning!加藤 学2026-09-17T06:30:1312100344652591489428
2100356254392836554Good morning. It is sunny there.Kanamokukagu2026-09-17T06:48:4802100344652591489428

Other available values include the reply URL, author identifiers and avatar URL, content and business identifiers, comment type, source keyword, collection time, image and video payloads, reply/share/view counts, the source item, and the no-data marker.

Use cases

  • Compare Reply text with Like count, Reply count, Share count, and View count to identify visible engagement around a conversation.
  • Reconstruct reply relationships with Reply comment ID, Parent comment ID, and Content ID.
  • Group replies by Author name, Author display ID, and Published time to review who participated and when.
  • Use Reply URL and Collection time to trace a collected record back to its public source and collection context.

Scope and boundaries

Each run collects public replies for one Twitter comment ID. The requested reply count is positive; results are returned in pages of up to 20 records and only publicly visible reply data available at collection time is covered.

  • Good for
  • When you need public Twitter replies connected to one comment or post conversation.
  • When you need reply text, authors, timestamps, links, parent relationships, and engagement counts for analysis.
  • Do not use for
  • When you need replies for multiple comment IDs in one request—run this App separately for each comment ID.
  • When you need private, deleted, or otherwise non-public Twitter replies.

Failure handling

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

  1. 1If no replies are returned, verify the Twitter comment ID and its public visibility.
  2. 2Retry later after rate limiting, temporary service unavailability, or a timeout.
  3. 3When the submission outcome is unknown, avoid immediately submitting the same task again to prevent duplicate collection.
  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.

  • Twitter comment IDcomment_idRequiredstring
    The numeric Twitter comment or post ID whose public replies will be collected. Provide one non-empty ID.
    Example2100344652591489428
  • Reply countcomments_spider_numOptionalinteger
    The expected number of public replies to collect. Provide a positive value; if omitted, the source service determines the collection amount and larger requests may take longer and return more records.
    Range1–Example10

Output

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

  • Business IDbiz_idstring
    The business grouping identifier returned with the reply record.
    Example2100344652591489428
  • Reply comment IDcomment_idstring
    The unique identifier of the collected Twitter reply.
    Example2100351577437663410
  • Reply textcomment_textstring
    The public text of the Twitter reply, preserved as returned by the source.
    Example@sousi526 Good morning!
  • Comment timecomment_timestring
    The source timestamp associated with the reply comment.
    ExampleWed Sep 16 22:30:13 +0000 2026

Sample data

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

output.example
{
  "biz_id": "2100344652591489428",
  "comment_id": "2100351577437663410",
  "comment_text": "@sousi526 Good morning!",
  "comment_time": "Wed Sep 16 22:30:13 +0000 2026",
  "comment_type": "2",
  "comment_url": "https://twitter.com/Katohakone3776/status/2100351577437663410",
  "comment_user_avatar_url": "https://pbs.twimg.com/profile_images/example.jpg",
  "comment_user_display_id": "Katohakone3776",
  "comment_user_id": "1486875573993426944",
  "comment_user_name": "加藤 学",
  "comment_videos": "<comment_videos>",
  "content_id": "2100344652591489428",
  "crawl_time": "2026-09-22T10:35:28",
  "image_urls": "<image_urls>",
  "keyword": "2100344652591489428",
  "like_count": "1",
  "parent_comment_id": "2100344652591489428",
  "publish_time": "2026-09-17T06:30:13",
  "reply_count": "1",
  "share_count": "0",
  "view_count": "34",
  "task_item": "2100344652591489428",
  "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/twitter-comment-reply",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}
View my API Keys →

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. (The prompt asks the AI to request your API key from you, so credentials never end up in chat history or shared configs.)

detail.access.mcp.composeHint

Pricing

Every 11 reply records

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

$0.002/ 11 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 / 11 records