EN

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

Developer
Pricing
From $0.003 / 30 records
Last updated
2026-09-18

Overview

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 IDContent titleContent URLAccount nameCollected atContent type
Eqm8TLNgBmoUlanzi UA50 50W エアチューブライト💡やわらかい光で自然なライティング✨https://www.youtube.com/shorts/Eqm8TLNgBmoUlanzi Japan(ウランジ)2026-08-31T09:49:46short
hY3nR8sTq2MCompact desk light setup for night shootinghttps://www.youtube.com/shorts/hY3nR8sTq2MUlanzi Japan(ウランジ)2026-08-30T11:12:08short

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.

Scope and boundaries

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.

  • Good for
  • 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
  • Do not use for
  • 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

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

  1. 1If no Shorts are returned, verify the account or channel name and confirm the account has publicly visible Shorts
  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. 4Partial success still returns Shorts already collected; missing items can be submitted again later
  5. 5If authentication fails, verify the API Key configured for the execution environment

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

  • YouTube account or channel nameaccount_nameRequiredstring
    The YouTube account or channel name whose public Shorts should be collected, such as UlanziJapan. Use 1 to 512 characters.
    ExampleUlanziJapan
  • Expected Shorts countcrawl_numRequiredinteger
    The 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.
    Range1–Example1

Output

Field structure of a single record, generated from the output.schema in manifest.json.

  • Content IDcontent_idstring
    Stable identifier of the Short. The source may return null on empty-result rows.
    ExampleEqm8TLNgBmo
  • Content URLcontent_urlstring
    Public link of the Short. The source may return null.
    Examplehttps://www.youtube.com/shorts/Eqm8TLNgBmo
  • Content titlecontent_titlestring
    Displayed title of the Short. The source may return null.
    ExampleUlanzi UA50 50W エアチューブライト💡やわらかい光で自然なライティング✨
  • Content textcontent_textstring
    Text associated with the Short. The source may return null.

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example
{
  "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
}

Integration

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=hello_moto/youtube-shorts-list",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)

detail.access.mcp.composeHint

Pricing

30 returned Shorts

Charged by the number of records successfully returned. Failed runs are not charged. Billed in units of 30 records; any partial unit is rounded up to 30 records.

$0.003/ 30 records
Per task submitted

Charged once per submitted run, regardless of how many records are returned.

$0.0001/ run

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
From $0.003 / 30 records