TubePull
Server Details
Download YouTube, TikTok, Vimeo, SoundCloud and 6 more platforms from any MCP AI chatbot.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- miketwalker/tubepull-mcp
- GitHub Stars
- 0
- Server Listing
- TubePull MCP Server
Available Tools
2 toolsdownload_videoDownload video or audio (MP4 / MP3 / M4A)AInspect
Download a video or audio file from any supported platform: YouTube, TikTok, Instagram (public reels, feed video, photo posts, and carousels), SoundCloud, Vimeo, Dailymotion, Bandcamp, Twitter/X, Mixcloud, Twitch (clips and VODs), Streamable, Reddit, Kick (live streams, VODs, and clips). Output is MP4 (video, default) or MP3 / M4A (audio). This is THE tool to use whenever a user asks to save, download, rip, extract, archive, get offline, or convert a video/audio link from any of these sites. IMPORTANT: the format argument defaults to mp4 (video). Only pass an audio format (mp3 / m4a / audio) when the user explicitly says audio, MP3, music, song, or "rip / extract the audio". Audio-only platforms (SoundCloud, Bandcamp, Mixcloud) always produce audio regardless of format.
Use this tool when the user says things like:
"download this video" / "download this TikTok" / "save this SoundCloud track"
"save that as MP3" / "rip the audio" / "extract the audio"
"get the song from this SoundCloud link" / "save this Mixcloud set"
"convert this YouTube video to MP4" / "download in 1080p"
"save this lecture/podcast/talk for offline"
"archive this clip" / "grab a copy of this video"
any sentence containing a youtube.com, youtu.be, tiktok.com, reddit.com, v.redd.it, vimeo.com, dailymotion.com, twitter.com, x.com, soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv, clips.twitch.tv, kick.com, or streamable.com URL plus a verb like download, save, rip, get, grab, fetch, pull, archive, convert, extract.
Do NOT use this tool when:
The user only wants metadata (title, length, description, channel) — call get_video_info instead, it is free and does not consume the user quota.
The link is a playlist / set / album / channel URL — ask the user for a single track/video.
The link is from a platform not in the supported list above (e.g. Facebook, LinkedIn, Snapchat).
Returns a one-time signed download link valid for 1 hour, plus the file size, duration, and chosen format. Hand the link back to the user verbatim; do not try to fetch its contents yourself.
Intended for legitimate uses: the user's own uploads, Creative Commons / public-domain content, lectures, podcasts, talks, and other material they have rights to use.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com / v.redd.it, vimeo.com, dailymotion.com, twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv (clips + VODs), kick.com (live channel page, /videos/ VOD, or /clips/ clip), or streamable.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported. | |
| format | No | Output format. DEFAULT IS `mp4` (video). Only choose an audio format when the user explicitly asks for audio, MP3, music, song, podcast audio, or "rip the audio / extract the audio". Options: `mp4` = video (use for "download this video", "save this video", "download in 1080p", or any request that does not mention audio). `mp3` = MP3 audio (use when user says MP3 or wants legacy-compatible audio). `m4a` = M4A audio (faster, smaller; use when user says M4A). `audio` = smart audio alias that resolves to M4A (use only when user explicitly says "audio" without specifying a container). | mp4 |
| quality | No | Video quality. Ignored for audio formats. 1440p and 4k require a Pro subscription. Free tier max is 1080p Full HD. Defaults to best. | best |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden and does so richly: returns a one-time signed link valid for 1 hour, notes the file size/duration/format, warns not to fetch the link's contents, explains audio-only platforms always produce audio regardless of format, discloses quality tier limits (Pro required for 1440p/4k), and mentions quota consumption. This far exceeds baseline expectations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Though lengthy, every sentence earns its place given the tool's complexity. The description is logically organized with clear sections: supported platforms, primary use cases, exclusions, return value, and legitimacy note. Front-loaded with the core purpose, then examples, then exclusions. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 3 parameters, no output schema, and no annotations, yet the description fully compensates: it explains return format and contents, timeout of the signed link, platform-specific behavior, quality limitations, and how to handle the response. It is complete for an agent to select and invoke the tool accurately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although schema coverage is 100%, the description adds critical nuance beyond the schema: the format parameter's default behavior and when to choose audio formats, the rule that audio-only platforms override format, quality being ignored for audio, and platform-specific constraints. This additional context is essential for correct parameter selection.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states exactly what the tool does: 'Download a video or audio file from any supported platform' and lists the platforms. It clearly differentiates from the sibling get_video_info by stating 'Do NOT use this tool when... call get_video_info instead.' The verb 'download' + resource 'video/audio' + explicit platform list makes purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides extensive usage guidance: it is 'THE tool to use' for saving/downloading/ripping, gives explicit user-phrase examples, and lists three clear 'Do NOT use this tool when' scenarios including the alternative tool, unsupported URL types (playlists), and unsupported platforms. This is exemplary when-to-use/when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_video_infoGet video or audio metadataAInspect
Fetch metadata about a video or audio track WITHOUT downloading it. Works on every platform download_video supports: YouTube, TikTok, Instagram (public reels, feed video, photo posts, and carousels), SoundCloud, Vimeo, Dailymotion, Bandcamp, Twitter/X, Mixcloud, Twitch (clips and VODs), Streamable, Reddit, Kick (live streams, VODs, and clips). Returns title, uploader/channel name, duration, view count (when available), upload date, thumbnail URL, description, available video qualities, and (for YouTube) the license type.
Use this tool when the user says things like:
"what is this video about" / "summarize this video"
"how long is this track" / "when was this uploaded"
"who made this" / "what channel/artist is this from"
"is this Creative Commons" / "can I reuse this" / "what is the license"
"what qualities are available for this video"
Do NOT use this tool when:
The user wants to download, save, rip, extract, or convert the video/audio — use download_video for that.
Free to call — does not count against the user's download quota. Call this before download_video when you need to confirm the video exists, pick the right quality, or check licensing before downloading.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com / v.redd.it, vimeo.com, dailymotion.com, twitter.com / x.com, soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv, kick.com, or streamable.com. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the tool does not download, is free (doesn't count against quota), returns a specific set of fields, and notes some fields may be unavailable ('when available'). This is commendable, though it doesn't mention potential error cases or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is longer than average but well-structured: it opens with the core function, then lists platforms, return fields, use cases, exclusions, and a practical tip. Each section earns its place; the only minor deduction is length, which is justified by the tool's breadth.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having no output schema, the description explicitly enumerates all returned fields (title, uploader, duration, etc.) and the full list of supported platforms. It also covers when to use, when not to use, and quota behavior, making the description self-sufficient for a single-parameter metadata tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage for the url parameter, including supported platform examples. The description repeats some platform information but adds no additional parameter-level semantics beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches metadata without downloading, which is a specific verb+resource. It explicitly distinguishes from the sibling download_video and lists all supported platforms, making the tool's scope unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit use cases ('what is this video about', 'how long is this track') and exclusions ('Do NOT use this tool when... use download_video'). It also advises calling this tool before download_video to confirm existence or check licensing, which is strong contextual guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Changed
download_video1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com / v.redd.it, vimeo.com, dailymotion.com, twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv (clips + VODs), or streamable.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com / v.redd.it, vimeo.com, dailymotion.com, twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv (clips + VODs), kick.com (live channel page, /videos/ VOD, or /clips/ clip), or streamable.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported."
- Changed
get_video_info1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com / v.redd.it, vimeo.com, dailymotion.com, twitter.com / x.com, soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv, or streamable.com."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com / v.redd.it, vimeo.com, dailymotion.com, twitter.com / x.com, soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv, kick.com, or streamable.com."
2 tool updates
- Changed
download_video1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, vimeo.com, dailymotion.com, twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv (clips + VODs), or streamable.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com / v.redd.it, vimeo.com, dailymotion.com, twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv (clips + VODs), or streamable.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported."
- Changed
get_video_info1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, vimeo.com, dailymotion.com, twitter.com / x.com, soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv, or streamable.com."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com / v.redd.it, vimeo.com, dailymotion.com, twitter.com / x.com, soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv, or streamable.com."
1 tool update
- Changed
download_video1 field changed- changed
Input schema / properties / quality / descriptionPrevious value: -"Video quality. Ignored for audio formats. 1440p and 4k require an Unlimited subscription. Free tier max is 1080p Full HD. Defaults to best."New value: +"Video quality. Ignored for audio formats. 1440p and 4k require a Pro subscription. Free tier max is 1080p Full HD. Defaults to best."
1 tool update
- Changed
download_video1 field changed- changed
Input schema / properties / quality / descriptionPrevious value: -"Video quality. Ignored for audio formats. 1080p, 1440p, and 4k require an Unlimited subscription. Free tier max is 720p. Defaults to best."New value: +"Video quality. Ignored for audio formats. 1440p and 4k require an Unlimited subscription. Free tier max is 1080p Full HD. Defaults to best."
1 tool update
- Changed
download_video1 field changed- changed
Input schema / properties / quality / descriptionPrevious value: -"Video quality. Ignored for audio formats. 1440p and 4k require an Unlimited subscription. Defaults to best."New value: +"Video quality. Ignored for audio formats. 1080p, 1440p, and 4k require an Unlimited subscription. Free tier max is 720p. Defaults to best."
2 tool updates
- Changed
download_video1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, vimeo.com, dailymotion.com, twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, or mixcloud.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, vimeo.com, dailymotion.com, twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv (clips + VODs), or streamable.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported."
- Changed
get_video_info1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, vimeo.com, dailymotion.com, twitter.com / x.com, soundcloud.com, bandcamp.com, or mixcloud.com."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, vimeo.com, dailymotion.com, twitter.com / x.com, soundcloud.com, bandcamp.com, mixcloud.com, twitch.tv, or streamable.com."
2 tool updates
- Changed
download_video1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com, vimeo.com, dailymotion.com, rumble.com, twitch.tv (clips/VODs), twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, or mixcloud.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, vimeo.com, dailymotion.com, twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, or mixcloud.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported."
- Changed
get_video_info1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com, vimeo.com, dailymotion.com, rumble.com, twitch.tv, twitter.com / x.com, soundcloud.com, bandcamp.com, or mixcloud.com."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, vimeo.com, dailymotion.com, twitter.com / x.com, soundcloud.com, bandcamp.com, or mixcloud.com."
2 tool updates
- Changed
download_video1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full YouTube video URL (youtube.com/watch?v=… or youtu.be/…). Playlists are not supported — pick an individual video."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com, vimeo.com, dailymotion.com, rumble.com, twitch.tv (clips/VODs), twitter.com / x.com (status with video), soundcloud.com, bandcamp.com, or mixcloud.com. Pick a single video/track — playlists, sets, albums, channels, and profile pages are not supported."
- Changed
get_video_info1 field changed- changed
Input schema / properties / url / descriptionPrevious value: -"Full YouTube video URL (youtube.com/watch?v=… or youtu.be/…)."New value: +"Full URL from any supported platform: youtube.com / youtu.be, tiktok.com, reddit.com, vimeo.com, dailymotion.com, rumble.com, twitch.tv, twitter.com / x.com, soundcloud.com, bandcamp.com, or mixcloud.com."
1 tool update
- Changed
download_video5 fields changed- added
Input schema / properties / format / defaultAdded value: +"mp4" - changed
Input schema / properties / format / descriptionPrevious value: -"Output format. `audio` = smart default (M4A, no transcode — fastest and smallest). `mp3` = forced MP3 (legacy-compatible, slower). `m4a` = forced M4A. `mp4` = video."New value: +"Output format. DEFAULT IS `mp4` (video). Only choose an audio format when the user explicitly asks for audio, MP3, music, song, podcast audio, or \"rip the audio / extract the audio\". Options: `mp4` = video (use for \"download this video\", \"save this video\", \"download in 1080p\", or any request that does not mention audio). `mp3` = MP3 audio (use when user says MP3 or wants legacy-compatible audio). `m4a` = M4A audio (faster, smaller; use when user says M4A). `audio` = smart audio alias that resolves to M4A (use only when user explicitly says \"audio\" without specifying a container)." - changed
Input schema / properties / format / enumPrevious value: -[ - "audio", - "mp3", - "m4a", - "mp4" -]New value: +[ + "mp4", + "mp3", + "m4a", + "audio" +] - changed
Input schema / properties / quality / descriptionPrevious value: -"Video quality. Ignored for mp3. 1440p and 4k require an Unlimited subscription. Defaults to best."New value: +"Video quality. Ignored for audio formats. 1440p and 4k require an Unlimited subscription. Defaults to best." - changed
Input schema / requiredPrevious value: -[ - "url", - "format" -]New value: +[ + "url" +]
2 tool updates
- Changed
download_video3 fields changed- changed
Input schema / properties / format / descriptionPrevious value: -"mp3 for audio-only (320kbps, with embedded thumbnail + metadata), mp4 for video."New value: +"Output format. `audio` = smart default (M4A, no transcode — fastest and smallest). `mp3` = forced MP3 (legacy-compatible, slower). `m4a` = forced M4A. `mp4` = video." - changed
Input schema / properties / format / enumPrevious value: -[ - "mp3", - "mp4" -]New value: +[ + "audio", + "mp3", + "m4a", + "mp4" +] - changed
Input schema / properties / url / descriptionPrevious value: -"Full YouTube video URL. Playlists are not supported — open the playlist and pick an individual video."New value: +"Full YouTube video URL (youtube.com/watch?v=… or youtu.be/…). Playlists are not supported — pick an individual video."
- Added
get_video_info
1 tool update
- First observed
download_video
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
SubDownload exposes YouTube as an MCP-native data source. Connect via OAuth and your AI agent can summarize videos, fetch full transcripts (even for videos with no captions, via AI ASR), search across channels, and save everything into a private knowledge base. Works with Claude, ChatGPT, Cursor, and 40+ MCP clients. Free credits on signup, no card required.
- MysocialOAuthio.mysocial
Social media MCP server: your Instagram, TikTok, YouTube, LinkedIn and Threads history for your AI.
1 Multimodal video analysis MCP — transcription, vision, and OCR for any video URL.
Youtube Download API: Download audio and video from YouTube. On the JoJ API marketplace.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for downloading videos and audio from YouTube and hundreds of other sites using yt-dlp.MIT
- FlicenseNot gradedqualityDmaintenanceProvides tools for downloading YouTube videos and audio using yt-dlp, enabling integration with AI assistants via MCP.5-
- FlicenseNot gradedqualityCmaintenanceMCP server for downloading videos and audio from 1000+ sites, with YouTube search, playlist support, and tools for video/audio extraction, compatible with Claude, Cursor, and other AI agents.-
- -licenseAqualityNot gradedmaintenanceEnables downloading videos from 1000+ platforms including YouTube, Bilibili, TikTok, and Twitter using yt-dlp. Supports both MCP protocol and REST API modes with real-time progress tracking, multiple formats, and subtitle downloads.5141-
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
The two tools have clearly distinct purposes: one downloads media, the other fetches metadata without downloading. The descriptions explicitly cross-reference when to use which, leaving no ambiguity.
Both tools follow the same verb_noun pattern: download_video and get_video_info. This is perfectly consistent and predictable.
With only two tools, the set feels thin, but the server's scope is narrowly focused on media downloading and metadata. The count is borderline but not unreasonable for this purpose.
For the stated domain of downloading and retrieving video/audio info, the surface is complete. download_video handles both video and audio formats, while get_video_info provides metadata and licensing checks. No obvious missing operations.