cloud-api-hub-youtube-downloader

Video channel owner ID

get_info_channelId

string The ID that YouTube uses to uniquely identify the channel that the video was uploaded to. Group: Specific video Info. Billing per call: 1 Credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_info_channelId"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Youtube video ID in expected format `(/^[a-zA-Z0-9-_]{11}$/)`

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026
- addedInput schema / required
```
Added value: +[
+  "id"
+]
```
First observedAug 19, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the burden and does disclose the return type (string) and a cost (1 credit per call). However, it omits other behavioral traits like error behavior, authentication requirements, or whether the value can be null.

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

Conciseness4/5

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

Very concise and front-loaded with the return value, followed by grouping and billing. The '**string**' prefix is slightly awkward but overall no wasted words.

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

Completeness4/5

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

For a simple single-field getter with rich schema coverage and no output schema, the description adequately explains the return value and cost. It does not restate the input parameter, but the schema covers it fully.

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 coverage is 100%, so the single id parameter is fully documented in the schema with format and example. The description adds no further parameter semantics, making the schema the sole source of parameter guidance.

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 returned value: the YouTube channel ID associated with a video. This distinguishes it from sibling fields like get_info_channelName, but it does not explicitly frame the tool as an action or say when to use it over the general get_info.

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 on when to use this tool versus the many sibling get_info_* tools or get_info itself. It only notes the billing cost, leaving the agent to infer that this retrieves a specific field.

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?