yt-consolidado

channels_getChannel

Retrieve a YouTube channel's raw data and normalized metadata by channel ID; optionally include the latest upload when recent activity is needed.

Instructions

Raw channel + normalizedMetadata — port of youtube-mcp-server (zubeid).

Layer: Data API. Quota: 1 unit; **+100 units** when ``include_latest_upload``
is true (the original resolves the newest upload with one search.list).
Set it to false when you only need country/joinedAt/emailsFound.

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": {
      "channelId": "<channelId>"
    },
    "name": "channels_getChannel"
  }
}

Input Schema

Name	Required	Description	Default
`channelId`	Yes
`include_latest_upload`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral trait: quota cost of 1 unit, jumping +100 units when include_latest_upload is true, plus the reason (an internal search.list call). It omits error behavior, auth requirements, and rate-limit handling, so the disclosure is partial rather than complete.

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

Conciseness3/5

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

The quota warning is front-loaded and useful, but 'port of youtube-mcp-server (zubeid)' and the 'Layer: Data API' label are provenance noise that does not help an agent invoke the tool. The core content is compact, but a meaningful share of the text does not earn its place.

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?

An output schema exists, so return values need not be described, and quota cost is covered. What is missing for a two-param data-fetch tool is sibling differentiation and channelId format expectations, leaving the definition adequate but with clear gaps.

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 0%, so the description must compensate. It explains include_latest_upload's cost and when to disable it, which is genuinely useful, but channelId is left entirely unexplained (format, whether handles/URLs are accepted) and the default-true behavior is only implied.

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

Purpose3/5

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

The description says it returns 'Raw channel + normalizedMetadata' for a channel, which conveys the resource and output shape, but never states the verb explicitly (fetch/retrieve a channel by ID). It also does not distinguish itself from the sibling get_channel_details, so an agent cannot tell from the text which one to pick.

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

Usage Guidelines3/5

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

There is real guidance for the include_latest_upload flag ('set it to false when you only need country/joinedAt/emailsFound'), which is a concrete when-to-use condition. However, there is no guidance on when to use this tool versus get_channel_details or search_channels, which is the more important routing decision.

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

Deploy Server