TubePull
Server Details
Download YouTube videos as MP3 or MP4 directly from any MCP-compatible AI chatbot.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 2 of 2 tools scored.
The two tools have entirely distinct purposes: one downloads videos/audio, the other retrieves metadata. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern: download_video and get_video_info, making the naming predictable and clear.
With only two tools, the server is minimal but appropriately scoped for its focused purpose of pulling YouTube videos and metadata. It could benefit from a search tool, but the count is reasonable for a narrow utility.
The server covers the core workflow of retrieving video metadata and downloading content. Minor gaps exist, such as no ability to list or search videos, but the main use case is well-supported.
Available Tools
2 toolsdownload_videoDownload YouTube video (MP3 or MP4)AInspect
Download a YouTube video to a file. Supports MP3 audio (saves as audio, extract audio, get audio, rip audio, save song, save music) and MP4 video (save video, save clip, archive video, download clip). Intended for legitimate uses such as offline access to your own uploads, Creative Commons or public-domain content, lectures, podcasts, talks, and other content you have rights to use. Returns a one-time signed download link valid for 1 hour. Triggers: "download YouTube video", "save YouTube as MP3", "get YouTube audio", "convert YouTube to MP4", "extract audio from YouTube", "save this video offline". Use get_video_info first if the user only wants metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full YouTube video URL (youtube.com/watch?v=… or youtu.be/…). Playlists are not supported — pick an individual video. | |
| format | Yes | Output format. `audio` = smart default (M4A, no transcode — fastest and smallest). `mp3` = forced MP3 (legacy-compatible, slower). `m4a` = forced M4A. `mp4` = video. | |
| quality | No | Video quality. Ignored for mp3. 1440p and 4k require an Unlimited subscription. Defaults to best. | best |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes the output as a one-time signed download link valid for 1 hour, notes that 1440p and 4k require an Unlimited subscription, and explains the smart default behavior for 'audio' format.
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?
Well-organized and front-loaded with the core action. Contains extra details like triggers and usage policies, which are helpful but slightly lengthy.
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?
Covers input, output behavior, limitations (no playlists, subscription requirements), and provides examples. No output schema, but the description sufficiently explains the return value.
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?
Adds significant context beyond schema: explains 'audio' as smart default (M4A, no transcode), contrasts 'mp3' as slower legacy, and clarifies quality parameter behavior (ignored for mp3, subscription requirements for high resolutions).
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?
Clearly states it downloads a YouTube video to file, distinguishes from sibling get_video_info for metadata-only use, and lists supported formats (MP3 audio and MP4 video).
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 triggers, legitimate use intentions, and explicitly recommends using get_video_info first for metadata. Does not state when not to use (e.g., for streaming), but otherwise clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_video_infoGet YouTube video metadataAInspect
Fetch metadata about a YouTube video without downloading it. Returns title, channel, duration, view count, upload date, thumbnail, full description, available video qualities, and the YouTube license type (Standard YouTube License vs Creative Commons). Use this for questions like "what is this video about", "how long is it", "who made it", "is this Creative Commons", or to decide what format/quality to pass to download_video. Free to call — does not count against the download quota.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full YouTube video URL (youtube.com/watch?v=… or youtu.be/…). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, description conveys safe read-only behavior, lists return data, and states no download cost. However, does not mention authentication or rate limits, but for a simple read operation this is acceptable.
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?
Two efficient sentences: first covers purpose and return, second covers usage and alternatives. No wasted words.
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?
Enough context for a simple one-parameter tool: purpose, return items, usage guidance, and sibling relationship. No output schema needed.
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?
Schema already describes the URL parameter at 100% coverage. Description adds no new parameter-level details, so 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?
Description clearly states it fetches metadata without downloading, lists specific return fields (title, channel, etc.), and distinguishes from sibling tool download_video by noting it's free and doesn't count against download quota.
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 example questions the tool answers, explicitly states when to use (free, no quota), and mentions alternative usage for download_video decisions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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!