yt-consolidado

search_channels

Search YouTube channels by query and retrieve enriched statistics, with options for result count, ranking order, and region to support creator discovery and channel research.

Instructions

Search channels enriched with stats — port of youtube-mcp search_channels.

Layer: Data API. Quota: 101 units (100 search + 1 channels batch).

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": {
      "query": "<query>"
    },
    "name": "search_channels"
  }
}

Input Schema

Name	Required	Default
`order`	No	relevance
`query`	Yes
`max_results`	No
`region_code`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.7/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 a concrete behavioral trait the schema cannot: an exact cost of 101 quota units (100 search + 1 channels batch) against the Data API. It stops short of stating auth requirements, whether results are paginated, or how many channels come back.

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?

It is short and front-loads the action, but roughly a third of the text is provenance ('port of youtube-mcp search_channels') that does not help an agent invoke the tool. The quota line earns its place; the port note does not.

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?

An output schema exists, so return values need no explanation, but for a four-parameter search tool with zero schema description coverage and no annotations the description is thin. Nothing explains ordering, result limits, or region filtering, leaving the agent to guess at invocation details.

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?

Schema description coverage is 0% and the description says nothing about query, order, max_results, or region_code — not even which are useful for narrowing results. The only hint, 'enriched with stats', concerns the output rather than any parameter's meaning.

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?

States a specific verb and resource: 'Search channels enriched with stats', which tells an agent what is retrieved and that results carry channel statistics. It does not differentiate from siblings such as search_videos, youtube_search, or channels_getChannel, so the agent must infer the distinction.

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 guidance on when to choose this over youtube_search or channels_getChannel, nor any stated prerequisites or exclusions. The quota figure hints that calls are expensive, but no explicit cost-vs-value decision guidance is given.

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

Deploy Server