Indique una palabra clave de YouTube y un recuento esperado para obtener videos públicos coincidentes, canales, visualizaciones y fechas de publicación.
YouTube Shorts List
Give a YouTube account name and an expected count to collect that account's public Shorts with titles, timing, duration, and view data
Original · en-USVolver a la traducción
Descripción general
Public YouTube Shorts show what a creator is testing, repeating, and getting attention for in short form. This app turns one account's public Shorts shelf into a row-level dataset: each Short keeps its title, link, account identity, duration, view figures, and collection time so teams can compare clips instead of scrolling a channel.
That is more useful than copying a few Shorts by hand because the same fields sit on every row. Titles, watch links, duration, and the view figures shown on the page stay aligned, which makes the result a practical source for short-form content audits, posting-rhythm checks, and view-performance snapshots.
Data notes
The data comes from the public Shorts list of the requested YouTube account. Records are ordered by publish time from newest to oldest, and the same content ID is kept only once across collected pages. View count appears both as the raw figure and as the on-page phrase; duration appears both as the clock text shown on the page and as the source duration string. Publish time, relative publish time, and collection time are stored as the source sends them, without an inferred timezone. Badge lists, cover images, and channel thumbnails are returned as source strings and may be empty. Deleted, private, age-restricted, or otherwise inaccessible Shorts are not covered.
What the results look like
Each record represents one public YouTube Short.
| Content ID | Content title | Content URL | Account name | Collected at | Content type |
|---|---|---|---|---|---|
| Eqm8TLNgBmo | Ulanzi UA50 50W エアチューブライト💡やわらかい光で自然なライティング✨ | https://www.youtube.com/shorts/Eqm8TLNgBmo | Ulanzi Japan(ウランジ) | 2026-08-31T09:49:46 | short |
| hY3nR8sTq2M | Compact desk light setup for night shooting | https://www.youtube.com/shorts/hY3nR8sTq2M | Ulanzi Japan(ウランジ) | 2026-08-30T11:12:08 | short |
Additional values include Displayed duration, Duration value, View count, View count text, Published at, Relative publish time, Task account, and No data.
Use cases
- Build a short-form theme inventory by grouping Content title with Content URL and comparing how often similar titles appear.
- Check posting rhythm by lining up Published at and Relative publish time across the returned Shorts.
- Compare attention by reading View count next to View count text and ranking clips that the page presents as more watched.
- Separate empty outcomes from real Shorts by checking No data together with Task account.
Alcance y límites
Each task collects public Shorts from one YouTube account. The requested count is an expected value and results may round up to a multiple of 30. A first collection may return up to 2,000 items and later collections 200 more; full collection is supported. Pull protection covers 1,000 result pages. Deleted, restricted, or inaccessible Shorts may be missing.
- Adecuada para
- When you need the public Shorts list for a specific YouTube account
- When you need Shorts titles, publish times, duration, and view figures for short-form analysis
- No usar para
- When you need regular long-form YouTube video lists rather than Shorts
- When you need comments, transcripts, or channel profile details rather than a Shorts list
- When you need short videos from a platform other than YouTube
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 1If no Shorts are returned, verify the account or channel name and confirm the account has publicly visible Shorts
- 2Retry later after rate limiting, temporary unavailability, or a timeout
- 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
- 4Partial success still returns Shorts already collected; missing items can be submitted again later
- 5If 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.
- YouTube account or channel name
account_nameObligatoriostringThe YouTube account or channel name whose public Shorts should be collected, such as UlanziJapan. Use 1 to 512 characters.EjemploUlanziJapan - Expected Shorts count
crawl_numObligatoriointegerThe number of Shorts you expect to collect. Results are returned in complete batches of 30, so the actual count may be rounded up. A remainder below 30 is still billed as 30 records. Larger values usually take longer and cost more.Rango1–Ejemplo1
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
- Content ID
content_idstringStable identifier of the Short. The source may return null on empty-result rows.EjemploEqm8TLNgBmo - Content URL
content_urlstringPublic link of the Short. The source may return null.Ejemplohttps://www.youtube.com/shorts/Eqm8TLNgBmo - Content title
content_titlestringDisplayed title of the Short. The source may return null.EjemploUlanzi UA50 50W エアチューブライト💡やわらかい光で自然なライティング✨ - Content text
content_textstringText associated with the Short. The source may return null.
Datos de ejemplo
Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.
{
"content_id": "Eqm8TLNgBmo",
"content_url": "https://www.youtube.com/shorts/Eqm8TLNgBmo",
"content_title": "Ulanzi UA50 50W エアチューブライト💡やわらかい光で自然なライティング✨",
"content_text": "<content_text>",
"account_name": "Ulanzi Japan(ウランジ)",
"account_display_id": "<account_display_id>",
"account_id": "<account_id>",
"biz_id": "UlanziJapan",
"article_type": "short",
"publish_time": "<publish_time>",
"raw_publish_time": "<raw_publish_time>",
"crawl_time": "2026-08-31T09:49:46",
"raw_duration": "<raw_duration>",
"video_duration": "<video_duration>",
"view_count": "<view_count>",
"view_count_text": "<view_count_text>",
"content_status": "RUNNING",
"is_collaboration": false,
"is_verified": false,
"is_verified_artist": false,
"keyword": "UlanziJapan",
"keyword_type": "accountShorts",
"account_badge_list": "<account_badge_list>",
"content_badge_list": "<content_badge_list>",
"cover_image_list": "<cover_image_list>",
"content_rich_thumbnail_list": "<content_rich_thumbnail_list>",
"channel_thumbnail_list": "<channel_thumbnail_list>",
"channel_description_links": "<channel_description_links>",
"co_creator_info": "<co_creator_info>",
"task_item": "UlanziJapan",
"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=hello_moto/youtube-shorts-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. (De forma predeterminada te guía para iniciar sesión y nunca te pide que envíes tu API Key en el chat.)
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 30 registros; cualquier unidad parcial se redondea a 30 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.