YouTube Channel and Video List Scraper MCP Server

Scrape YouTube videos and channels

scrape_youtube_videos_channels

Read-onlyIdempotent

Scrape public YouTube channels, playlists, and search results into structured video and channel rows with views, dates, lengths, subscribers, and links—no login required.

Instructions

Scrape public YouTube channels, playlists, and search results: one row per video with title, rounded views, relative date, and length, and a row per channel with subscribers, total views, and links. It does not open single video pages. No YouTube login.

Input Schema

Name	Required	Description
`urls`	No	Channel, @handle, playlist, or search result addresses, or a bare channel ID or @handle. Up to 200 sources a run, counted with search terms. A single video address returns one free row: this actor does not open video pages. Clay users: wrap a column in a one item list.
`channel_tab`	No	Which channel list to read: videos (default), shorts, or streams.
`search_terms`	No	Terms to search on YouTube. Each term returns videos in YouTube's order, for a logged out US visitor. Clay users: wrap a column in a one item list.
`max_charge_usd`	No	Optional. The run stops before a charge that would pass this amount. Reports are always delivered.
`include_channel_row`	No	yes (default) adds one row per channel source with subscribers, total views, video count, joined date, country, and links. no skips it.
`max_videos_per_source`	No	Per channel, playlist, or search term. Default 30, maximum 5000. Set 0 on a channel to get only its channel row.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare this as a read-only, idempotent, non-destructive, open-world operation. Beyond that, the description adds that only public YouTube content is scraped, no login is required, and single video pages are not opened. It also explains the output row structure, though it does not discuss pagination or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tightly written sentences with no filler. It front-loads the supported source types and immediately follows with the key output and exclusion details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter scraping tool with no output schema, the description gives enough context about what is returned per video and per channel. It also covers public-only access, no login, and the single-video-page limitation. Minor operational details such as pagination and error behavior are left to the schema or omitted, but the definition is broadly sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters are already well documented in the input schema. The description does not add parameter-specific meaning beyond stating the overall scraped output. Baseline 3 is appropriate because the schema is doing the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource set: scrape public YouTube channels, playlists, and search results. It also describes the row-level output for videos and channels, making the tool's purpose immediately clear. The explicit exclusion of single video pages further distinguishes its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies use for public channel, playlist, and search-result scraping and explicitly states that it does not open single video pages. It does not provide alternative tools, but there are no sibling tools listed. The no-login constraint also clarifies when this tool is applicable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

scrape_youtube_videos_channelsA