logo
languageESdown
menu

Twitter Account List

Give a Twitter account ID and a maximum post count to get that account's public post list with content IDs and publish times

Original · en-USVolver a la traducción

Descripción general

Want a working inventory of what a Twitter account posts, without scrolling the profile by hand? Give this App a public Twitter account ID and a maximum post count, and it returns that account's public posts as individual records. Each record carries the content ID, publish time, collection time, and the account identifier stored with the post, so research and monitoring teams can treat the timeline as a dataset rather than a webpage.

A profile page is built for reading one post at a time. This list is built for comparison: you can line up publish times, keep content IDs next to the account they came from, and see when each row was collected. The values are the public identifiers and timestamps captured with each post, not reconstructed from screenshots.

Data notes

The records come from a Twitter account's public post list and are ordered from newest to oldest by publish time. Each row is one public post, and the same content ID appears only once. Keyword and business ID repeat the account identifier stored on the post. Publish time, collection time, and clean update time are timestamps without an explicit timezone. Private, protected, deleted, or login-only posts are not included.

What a result looks like

Each record is one public post from the requested account:

Content IDPublish timeKeywordBusiness IDCollection timeRecord ID
20925179666048700702023-01-07T16:15:39161163758892181504016116375889218150402026-08-26T17:24:166a8eb0c1a247355e51208cb2
20925184719891828582023-01-07T16:15:39161163758892181504016116375889218150402026-08-26T17:24:166a8eb0c1a247355e51208cb0

Keyword type, source identifier, clean update time, and the no-data flag are also returned when present.

Example uses

  • Build an account inventory by lining up Content ID, Publish time, and Keyword for the public posts you collected.
  • Confirm you collected the intended account with Business ID before using Content ID in a report.
  • Track freshness with Collection time next to Publish time to see when each post was captured.

Alcance y límites

Each run processes 1 Twitter account ID. The requested post count is a strict maximum and the actual return will not exceed that value. Pull protection covers 1,000 result pages. Only publicly visible posts are covered.

  • Adecuada para
  • When you need a public post list for a specific Twitter account
  • When you need content IDs, publish times, and collection timestamps for those posts
  • No usar para
  • When you need private, protected, deleted, or login-only posts
  • When you need tweet text, media, engagement counts, or profile details rather than post identifiers and timestamps

Gestión de fallos

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

  1. 1If no data is returned, verify the Twitter account ID and confirm the account has publicly visible posts
  2. 2Retry later after rate limiting, temporary 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

Entrada

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

CampoNombre de negocioTipoObligatorioPredeterminadoEnum / RestriccionesEjemploDescripción
account_idTwitter account IDstringSí——1611637588921815040The Twitter account ID to collect, such as 1611637588921815040. Each run processes one account ID. Use 1 to 512 characters.
crawl_numMaximum postsintegerSí—1–20001The maximum number of public posts to collect for this account. The actual return will not exceed this value. Larger values take more time.

Salida

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

CampoNombre de negocioTipoEjemploDescripción
biz_idBusiness IDstring1611637588921815040Business identifier stored on the post record; it may be empty.
clean_update_timeClean update timestring2026-08-26T17:24:17Timestamp when this record was last cleaned; it may be empty and has no explicit timezone.
content_idContent IDstring2092517966604870070Public identifier of the Twitter post; it may be empty.
crawl_timeCollection timestring2026-08-26T17:24:16Timestamp when this post was collected; it may be empty and has no explicit timezone.
cur_idRecord IDstring6a8eb0c1a247355e51208cb2Identifier of this collected row; it may be empty.
keywordKeywordstring1611637588921815040Account identifier stored on this post record; it may be empty.
keyword_typeKeyword typestringaccountType label stored with the keyword, such as account; it may be empty.
no_dataNo databooleanfalseWhether this identifier produced no public posts.
publish_timePublish timestring2023-01-07T16:15:39Timestamp when the post was published; it may be empty and has no explicit timezone.
source_itemSource identifierstring1611637588921815040Original account identifier associated with this record.

Schema del registro

La salida se devuelve registro a registro. detail.output.idFieldHint

output.schema
{
  "type": "object",
  "properties": {
    "biz_id": {
      "type": "string",
      "title": "Business ID",
      "description": "Business identifier stored on the post record; it may be empty.",
      "prefill": "1611637588921815040"
    },
    "clean_update_time": {
      "type": "string",
      "title": "Clean update time",
      "description": "Timestamp when this record was last cleaned; it may be empty and has no explicit timezone.",
      "prefill": "2026-08-26T17:24:17"
    },
    "content_id": {
      "type": "string",
      "title": "Content ID",
      "description": "Public identifier of the Twitter post; it may be empty.",
      "prefill": "2092517966604870070"
    },
    "crawl_time": {
      "type": "string",
      "title": "Collection time",
      "description": "Timestamp when this post was collected; it may be empty and has no explicit timezone.",
      "prefill": "2026-08-26T17:24:16"
    },
    "cur_id": {
      "type": "string",
      "title": "Record ID",
      "description": "Identifier of this collected row; it may be empty.",
      "prefill": "6a8eb0c1a247355e51208cb2"
    },
    "keyword": {
      "type": "string",
      "title": "Keyword",
      "description": "Account identifier stored on this post record; it may be empty.",
      "prefill": "1611637588921815040"
    },
    "keyword_type": {
      "type": "string",
      "title": "Keyword type",
      "description": "Type label stored with the keyword, such as account; it may be empty.",
      "prefill": "account"
    },
    "no_data": {
      "type": "boolean",
      "title": "No data",
      "description": "Whether this identifier produced no public posts.",
      "prefill": false
    },
    "publish_time": {
      "type": "string",
      "title": "Publish time",
      "description": "Timestamp when the post was published; it may be empty and has no explicit timezone.",
      "prefill": "2023-01-07T16:15:39"
    },
    "source_item": {
      "type": "string",
      "title": "Source identifier",
      "description": "Original account identifier associated with this record.",
      "prefill": "1611637588921815040"
    }
  },
  "required": [],
  "additionalProperties": 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.

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": {
    "hello_moto__twitter-account-list": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=hello_moto/twitter-account-list",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

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

Task start

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

0,0001 US$/ ejecución
Per record returned

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

0,002 US$/ 20 registro

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
Rellena primero los parámetros obligatorios
Desde 0,002 US$ / 20 registro