YouTube Shorts Scraper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from https://console.apify.com/account/integrations. The server lists its tool without a token, but a tool call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_youtube_shortsA | Read YouTube Shorts from channel Shorts tabs, from a YouTube search with the Shorts filter, or from Short links. Returns one row per Short with exact views, likes, comment count, publish date, hashtags, and channel, plus a free report row per source. Channels can be sorted by latest, popular, or oldest. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool there is no possibility of misselection; its purpose (fetching YouTube Shorts metadata plus a report row) is explicit and unambiguous. The three input modes (channel tab, search filter, short link) are handled within one clearly documented entry point rather than competing tools.
The single name get_youtube_shorts is a clear verb_noun snake_case pattern that matches the server's stated purpose. No mixed conventions exist to cause confusion.
One tool is thin even for a focused scraper: the three distinct source modes (channel, search, link) and sorting options are all collapsed into a single parameterized call. It works, but a slightly larger set of source-specific tools could be easier to invoke correctly.
As a read-only scraping domain, no create/update/delete operations are needed, and the tool covers the main entry points (channel Shorts tab, filtered search, short links) with rich output fields and sorting. Minor gaps remain around result limits/pagination and any per-video detail or download operation, which an agent would have to work around.