YouTube Shorts CLI

Parse YouTube Shorts from your agent session.

Fastdown gives AI coding agents a command-line and MCP surface for public short-video links, including YouTube Shorts workflows that need metadata, media URLs or local files.

One installer, three surfaces

Start with the CLI, expose it as MCP, and keep the API available for custom automation.

CLI

Terminal friendly

Use fast-download parse, download, quota and billing from scripts.

MCP

Agent friendly

Run fast-download mcp --stdio and let the agent call download_video.

API

Integration friendly

Use the Cloudflare Worker API when a backend wants structured parse responses.

Launch-ready workflow

The fastest demo is to show an agent installing Fastdown, logging in, then parsing a public YouTube Shorts URL.

  1. 1Open Codex, Claude Code or Open Code and paste the Fastdown setup prompt from the homepage.
  2. 2Authenticate once with Google OAuth and restart the agent app if it was already open.
  3. 3Ask for a public YouTube Shorts link to be parsed or saved locally.

What a parse returns

A parse is not a download button. It is structured output: every rendition, whether it carries a watermark, and how much quota is left.

$ fast-download download "https://youtube.com/shorts/xxxx" --json
{
  "platform": "youtube_shorts",
  "title": "60-second pasta",
  "media": [{ "quality": "1080p", "ext": "mp4", "url": "https://..." }],
  "saved_to": "/Users/you/Downloads/fast-download/60-second-pasta.mp4"
}

Coverage and limits

Stated plainly, because a tool that hides its edges is a tool you cannot build on.

CapabilityStatusNotes
YouTube ShortsSupported/shorts/ URLs and short share links
Full-length YouTube videosNot supportedUse yt-dlp; Fastdown is scoped to short-form
Age-restricted videosNot supportedRequires a signed-in session
Member-only videosNot supportedPayment wall, no public stream
Max resolutionSource dependentUsually 1080p vertical
SubtitlesNot returnedMetadata and media only

Boundaries and compliance

Four constraints that make the tool safe to put inside an automated workflow.

Questions people actually ask

Can this download full YouTube videos?

No. Fastdown handles Shorts only; for long-form video and channel archiving, yt-dlp is the right tool and we say so on the docs page.

Why not just use yt-dlp?

For a one-off shell command, use yt-dlp. Use Fastdown when an agent needs a typed tool that returns JSON and a saved path without constructing a command line.

What resolution do Shorts come back in?

Whatever the uploader provided — usually 1080p vertical. Fastdown never upscales and never re-encodes.

Does it strip the YouTube overlay?

The source stream has no burned-in UI; overlays you see in the player are rendered by the page, not baked into the file.

Three ways people actually run it

The Shorts URL is usually the only thing you have, so every entry point starts there.

  1. 1Clip research inside an IDE — Ask the agent to fetch a Short, then let it read the file for captions or frame grabs — no context switch to a browser.
  2. 2Batch of Shorts from a spreadsheet — Loop the CLI over a column of URLs; each row returns JSON, and failed rows are identifiable by exit code instead of by squinting at output.
  3. 3One-off save — fast-download download <url> with no flags writes the file to ~/Downloads/fast-download and prints one line.