Skip to main content
Glama

cloud-api-hub-youtube-downloader

by com.jojapi
OverviewAdmin

Video/audio streams muxer

get_mux

object Video & Audio Muxer which generates directly downloadable links from a Youtube video. Billing per call: 10 Credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoYoutube video ID in expected format `(/^[a-zA-Z0-9-_]{11}$/)`
codecNo**string** Sets the video codec for downloads. The desired video codec (e.g., h264, vp9, av1). H264 codec is set by default. Throws: Error if the provided codec is not valid.
endTimeNo**datetime or unsigned integer** Trims video or audio with reference to end time. Time in [HH:mm:ss](https://www.w3.org/TR/NOTE-datetime) format or in milliseconds.
qualityNo**string** Sets the video quality for downloads. The desired video quality (e.g. 144, 240, 360, 480, 720, 1080, 1440, 2160, 4320, max). 720 quality is recommended for phones. Throws: Error if the provided quality is not valid.
languageNo**string** specifies the language of audio to download when a youtube video is dubbed. E.g.: en / ru / cs / ja / es-US / ...
audioOnlyNo**boolean** Enables downloading only audio.
startTimeNo**datetime or unsigned integer** Trims video or audio with reference to start time. Time in [HH:mm:ss](https://www.w3.org/TR/NOTE-datetime) format or in milliseconds.
videoOnlyNo**boolean** Enables downloading only video.
watermarkNo**array** Adds an image to the video. List of values: 1. *URL 2. position: topLeft, topRight, bottomLeft, bottomRight, center (default) or pixel coordinates in x:y format from top left corner. 3. Scale (%widest side) 4. Transparency between 0 and 1 (none)
audioFormatNo**string** Sets the audio format for downloads (e.g., mp3, ogg, wav). Default: mp3 Throws: Error if the provided format is not valid.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the full behavioral burden. It mentions billing and hints at an object return, but omits output format, processing time, permissions, or other side effects, leaving significant ambiguity for a code-heavy tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only two sentences, front-loading the core purpose and cost without redundancy or filler. Every word serves a function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex with 10 parameters and no output schema or annotations. The description fails to explain return value shape, typical usage patterns, or edge-case interactions, leaving major gaps for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with each parameter detailed in the schema. The tool description adds no parameter-specific meaning beyond the muxing context, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates directly downloadable links from a YouTube video using video and audio muxing. It distinguishes from sibling info tools, though it does not explicitly differentiate from get_download.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The billing mention is a cost note, not usage direction, and no sibling tools are referenced.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All cloud-api-hub-youtube-downloader toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources