Xiaohongshu Keyword Search
Search one Xiaohongshu keyword and return matching content identifiers with collection metadata.
Original · en-USVolver a la traducción
meme_todayDescripción general
Researching how a topic appears in Xiaohongshu search often starts with finding a dependable set of matching content identifiers. This app turns one search keyword into a structured collection of matching items, keeping the keyword and collection context beside each identifier so the dataset remains understandable after it is exported or joined with other research material.
The result is useful as a discovery index: it shows which content items were associated with a brand, product, topic, or campaign at collection time. It is especially suited to building repeatable monitoring sets, comparing the content populations found for different terms, and preparing identifiers for later analysis without manually recording items from search pages.
Data notes
Each record represents one item associated with the submitted Xiaohongshu keyword. Content identifiers are de-duplicated within the returned dataset. Matched keyword, Source item, and Business ID preserve the collection context and may repeat across many records from the same search. Effective update time is returned without timezone information, so it should not be treated as an absolute cross-region timestamp without additional context. Account unique ID may be unavailable for some records.
The collection contains identifiers and collection metadata, not the full post body, title, media, engagement totals, comments, or a complete author profile. A No-data marker distinguishes task metadata that reports no matching content from ordinary matched records.
What a result looks like
Each row is one matched content item or a no-data marker associated with the search keyword.
| Content ID | Matched keyword | Effective update time | Business ID | No-data marker |
|---|---|---|---|---|
| 6a8ffa18000000000402a03c | 蓝牙耳机 | 2026-08-27T16:56:13 | 蓝牙耳机 | No |
| 6a8ff9c900000000260068c2 | 蓝牙耳机 | 2026-08-27T16:56:13 | 蓝牙耳机 | No |
Account unique ID and Source item are also available when supplied with the record.
Use cases
- For topic discovery, group rows by Matched keyword and count distinct Content ID values to compare the searchable content population associated with each term.
- For monitoring, repeat a keyword collection and compare Content ID sets while using Effective update time as source-provided context for newly observed items.
- For provenance checks, compare Matched keyword, Source item, and Business ID to confirm which search context produced each content item before combining datasets.
- For data-quality review, filter on No-data marker and missing Account unique ID values to separate empty-search metadata from usable matched records.
Alcance y límites
One keyword per task with an expected result count from 1 to 200; results are returned in complete batches of 20 and may be rounded up; coverage is limited to records available through Xiaohongshu keyword search.
- Adecuada para
- When you need content identifiers returned by a Xiaohongshu keyword search for a brand, product, topic, or campaign.
- When you need a structured list that connects each matched content item with its search keyword and collection metadata.
- No usar para
- When you need full post text, media, engagement metrics, comments, or complete author profiles.
- When you need an immediate single-record lookup rather than a background keyword collection task.
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 1If no matching records are returned, verify the keyword or try a shorter and broader search phrase.
- 2Keep completed records after a partial success; resubmit the same input after a failed or expired task.
- 3Retry later after rate limiting, temporary service unavailability, or a timeout.
- 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.
- Search keyword
keywordObligatoriostringA brand, product, topic, or phrase to search on Xiaohongshu. Each task accepts one keyword from 1 to 512 characters.Ejemplo蓝牙耳机 - Expected result count
crawl_countObligatoriointegerExpected number of search results, from 1 to 200. Results are returned in complete batches of 20, so the actual count may be rounded up.Rango1–200Ejemplo20
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
- Content ID
content_idstringUnique identifier of the matched Xiaohongshu content item.Ejemplo6a8ffa18000000000402a03c - Matched keyword
keywordstringSearch keyword associated with the collected content item.Ejemplo蓝牙耳机 - Effective update time
effective_update_timestringTimestamp associated with the collected record; the source does not specify a timezone.Ejemplo2026-08-27T16:56:13 - Account unique ID
account_unique_idstringUnique account identifier when available; this value may be missing.Ejemploaccount_example_001
Datos de ejemplo
Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.
{
"content_id": "6a8ffa18000000000402a03c",
"keyword": "蓝牙耳机",
"effective_update_time": "2026-08-27T16:56:13",
"account_unique_id": "account_example_001",
"biz_id": "蓝牙耳机",
"source_item": "蓝牙耳机",
"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": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=meme_today/xiaohongshu-keyword-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
Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran. Se factura en unidades de 20 registros; cualquier unidad parcial se redondea a 20 registros.
Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.
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éditosPruébalo ahora
Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.