cloud-api-hub-youtube-downloader

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

Name	Required	Description
`id`	Yes	Youtube video ID in expected format `(/^[a-zA-Z0-9-_]{11}$/)`
`codec`	No	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.
`endTime`	No	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.
`quality`	No	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.
`language`	No	string specifies the language of audio to download when a youtube video is dubbed. E.g.: en / ru / cs / ja / es-US / ...
`audioOnly`	No	boolean Enables downloading only audio.
`startTime`	No	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.
`videoOnly`	No	boolean Enables downloading only video.
`watermark`	No	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)
`audioFormat`	No	string Sets the audio format for downloads (e.g., mp3, ogg, wav). Default: mp3 Throws: Error if the provided format is not valid.
`subtitleLang`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 1, 2026
- changedInput schema / properties / audioOnly / example
```
Previous value: -"false"New value: +false
```
- changedInput schema / properties / audioOnly / type
```
Previous value: -"string"New value: +"boolean"
```
- addedInput schema / properties / subtitleLang
```
Added value: +{
+  "type": "string"
+}
```
- changedInput schema / properties / videoOnly / example
```
Previous value: -"false"New value: +false
```
- changedInput schema / properties / videoOnly / type
```
Previous value: -"string"New value: +"boolean"
```
- addedInput schema / properties / watermark / items
```
Added value: +{
+  "type": "string"
+}
```
- changedInput schema / properties / watermark / type
```
Previous value: -"string"New value: +"array"
```
- addedInput schema / required
```
Added value: +[
+  "id"
+]
```
First observedAug 19, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully discloses billing at 10 credits per call and implies a non-destructive link-generation operation, but it does not cover permissions, rate limits, link lifetime, or other operational side effects.

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 two short sentences with no wasted content. It front-loads the core purpose and adds the important billing detail without unnecessary elaboration.

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

Completeness3/5

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

For an 11-parameter tool with no annotations and no output schema, the description is fairly thin. It states the core output as downloadable links and mentions billing, but it lacks return-format details and operational context that would help an agent call the tool with confidence.

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 91%, so the input schema already explains nearly all parameters in detail. The description adds no additional parameter-level meaning beyond the high-level muxing purpose, making the baseline score 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 states a specific verb and resource: it is a video/audio muxer that generates directly downloadable links from a YouTube video. This clearly separates it from get_info_* metadata tools, though it does not explicitly distinguish itself from the sibling 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?

There is no explicit guidance on when to use this tool versus alternatives such as get_download or the get_info_* tools. The intended use is only implied by the phrase 'generates directly downloadable links from a Youtube video.'

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?