logo
ES

Twitter Comment Collection

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

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

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 IDComment textComment author handlePublish timeLike countNo-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:552No

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.

Alcance y límites

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

  • Adecuada para
  • 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.
  • No usar para
  • When you need private, deleted, or non-public Twitter comments.
  • When you need an immediate single-comment lookup rather than an asynchronous collection task.

Gestión de fallos

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

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

Entrada

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

  • Twitter post IDpost_idObligatoriostring
    The ID of one public Twitter post whose comments should be collected. The upstream accepts up to 512 characters.
    Ejemplo2102028592125473050
  • Requested comment countcomments_spider_numObligatoriointeger
    The number of comments to request for the post. The upstream documentation does not specify a maximum; provide the desired count explicitly.
    Ejemplo10

Salida

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

  • Business IDbiz_idstring
    Business grouping identifier associated with the source post.
    Ejemplo2102028592125473050
  • Comment IDcomment_idstring
    Unique identifier of the collected Twitter comment.
    Ejemplo2102029309472805246
  • Comment textcomment_textstring
    Text content of the collected comment, including mentions, line breaks, and links when supplied.
    Ejemplo@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.
    EjemploMon Sep 21 13:36:55 +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": "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
}

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",
      "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

per accepted task

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

0,001 US$/ ejecución
per returned 11 comment

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

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