A
licenseB
qualityD
maintenanceEnables comprehensive YouTube data access including video details, playlists, channels, comments, search, and subtitle operations through the YouTube Media Downloader API.
19
MIT
youtube-downloader-api
by com.jojapi
Server Details
YouTube Downloader API: The YouTube Downloader API enables fast and easy downloading of YouTube.
- 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.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
D1.5/5.0
Tool DescriptionsD
Average 1/5 across 1 of 1 tools scored.
Server CoherenceC
Disambiguation5/5
With only one tool, there is no possibility for confusion or overlap. The single tool's purpose is clearly unique by default.
Naming Consistency2/5
The tool name 'get_fetch_media' is internally inconsistent, combining two synonymous verbs ('get' and 'fetch') into one name. This violates standard verb_noun naming conventions and creates unnecessary redundancy.
Tool Count2/5
A YouTube downloader API with exactly one tool is far too thin for the apparent scope. The tool count rule penalizes having only a single tool for a domain that clearly requires multiple operations.
Completeness1/5
The server's purpose is to be a YouTube downloader API, yet it only exposes 'fetch_media'. There are no operations for actual downloading, format selection, status tracking, or cancellation, leaving the surface severely incomplete.
Available Tools
1 toolget_fetch_mediafetch_mediaDInspect
fetch_media Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No |
Tool Definition Quality
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full responsibility for disclosing behavior. It only mentions billing, not side effects, permissions, return values, or any operational traits. The agent cannot infer what happens when the tool is called.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short, but this is under-specification rather than conciseness. The single sentence adds no informative value; it merely repeats the tool name and a billing note. It wastes the opportunity to convey essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Even though the tool is simple (one parameter, no output schema), the description is completely inadequate. It fails to explain what media is fetched, how the URL is processed, or what the expected outcome is. The agent has no basis to determine if this tool is suitable for a task.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has one parameter 'url' with an example, but the description does not mention it at all. With schema description coverage at 0%, the description should compensate, but it adds no meaning beyond the schema's existence. The URL's purpose and format are unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description only repeats the tool name and mentions billing ('fetch_media Billing per call: 1 Credits.'). It does not state what the tool does, what resource it acts on, or what 'fetch_media' means in terms of behavior. This is a tautology, failing to clarify the purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. There is no indication of when to use this tool, what problem it solves, or any alternative tools. The description offers zero context for appropriate invocation.
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!
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables downloading MP3 audio files from YouTube videos by providing a YouTube URL through the Youtube Mp310 API.1MIT
- AlicenseCqualityDmaintenanceEnables users to stream or download YouTube video information and direct links via the Ytstream API. It supports geographic optimization and language selection for better download speeds and audio availability.1MIT
- AlicenseDqualityDmaintenanceEnables downloading content from various social media platforms through a unified API. Provides a single tool to download media from multiple social networks using the Social Download All In One service.1MIT