logo
ES

Twitter Comment Replies

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

Original · en-USVolver a la traducción

Recopilación de datosSocial MediaX (Twitter)Reviews & Ratings
Desarrollador
hello_moto
Precios
Desde 0,002 US$ / 11 registros
Última actualización
2026-10-12

Descripción general

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.

Alcance y límites

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.

  • Adecuada para
  • 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.
  • No usar para
  • 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.

Gestión de fallos

Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.

  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.

Entrada

Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.

  • Twitter comment IDcomment_idObligatoriostring
    The numeric Twitter comment or post ID whose public replies will be collected. Provide one non-empty ID.
    Ejemplo2100344652591489428
  • Reply countcomments_spider_numOpcionalinteger
    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.
    Rango1–Ejemplo10

Salida

Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.

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

Datos de ejemplo

Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.

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
}

Integración

Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Data Hub); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino. Esta App se ejecuta de forma asíncrona y se puede cancelar a mitad de camino: Tras la cancelación, la ejecución se detiene. Los registros ya entregados se conservan y se facturan.

Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.

Configuración del cliente

Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.

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>" }
    }
  }
}
Ver mis API Keys →

Deja que la IA lo configure por ti

¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (El prompt le pide a la IA que te solicite tu API Key, de modo que las credenciales nunca queden en el historial de chat ni en configuraciones compartidas.)

detail.access.mcp.composeHint

Precios

Every 11 reply records

Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran. Se factura en unidades de 11 registros; cualquier unidad parcial se redondea a 11 registros.

0,002 US$/ 11 registros
Per task submitted

Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.

0,0001 US$/ ejecución

Los distintos eventos de facturación se acumulan de forma independiente. Consulta cada elemento para más detalles. Las ejecuciones fallidas no se cobran.

Ver créditos

Pruébalo ahora

Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.

Ejemplo
Los parámetros se validan contra input.schema antes del envío
Desde 0,002 US$ / 11 registros