mcp-youtube-channel-transcript-extractor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations |
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_channel_statsA | Resolve a company domain, or a YouTube handle, to that company's YouTube channel. Returns the subscriber count, the stable UC channel id, channel name, creation date and description, as one flat Clay ready row. Subscriber counts are rounded by YouTube above roughly a thousand subscribers, on the page and in its official API alike, and the row flags that. Optional transcript pulling is available and is CURRENTLY GATED by YouTube: the caption track list is readable and the caption content endpoint returns an empty body without a proof of origin token, which the row reports as not_extractable rather than as a video having no captions. A company with no channel reports youtube_status not_found. Read youtube_status before any count. Use it to look up one known company channel per call; it does not search YouTube, list a channel's videos, or return video detail, and the package name mentions transcripts only because transcript pulling is an option. No API key needed. Read only; requires an APIFY_TOKEN and consumes Apify credits per call. |
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 nothing to confuse it with, and the description clearly enumerates what it does (domain/handle → channel stats) and what it does not do (search, video listing, video detail). The only mild internal blur is that the tool name advertises transcripts while the body frames them as a gated option, but that is a scoping note, not a tool-selection ambiguity.
The single tool follows a clean snake_case verb_noun pattern (get_youtube_channel_stats). No mixing of conventions or vague verb styles is present to break predictability.
One tool is thin for a server that also implies transcript extraction and channel resolution; resolving, stats, and transcript pulling are collapsed into a single overloaded call. It is not mis-scoped enough to be wrong, but it sits at the borderline of too few.
Channel lookup and stats are covered, but the headline transcript capability is effectively unusable (caption content gated, reported as not_extractable), and there is no video listing, video detail, or multi-channel/batch operation. An agent can still retrieve channel stats, so gaps are notable rather than fatal.