Skip to main content
Glama

search_channels

Search YouTube for channels by query, with sort options for relevance, date, rating, view count, title, or video count.

Instructions

Searches YouTube for channels matching the specified query. You can specify a sort order for the results (default: rating).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query to find YouTube channels.
sortByNoSort order for search results: relevance, date, rating (default), viewCount, title, or videoCount.rating
Behavior2/5

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

No annotations provided, so the description must carry full burden. It mentions default sort order but omits details such as result limits, pagination, rate limits, or error behavior. Minimal behavioral disclosure.

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?

Two concise sentences that front-load the core purpose and cover the main parameter. No redundant information; every sentence adds value.

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?

Missing critical context: no output schema, so description should explain return format or behavior. Also lacks details on result count, pagination, or the nature of 'channels'. Incomplete for a search tool.

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%, and the description adds only a note about default sort order, which is already in the schema. No additional meaning beyond what the input schema provides, earning a baseline score.

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 action (searches) and resource (channels), with explicit query and sort order. However, it does not differentiate from the sibling 'search_videos' tool, missing an opportunity to clarify scope.

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 alternatives like 'search_videos'. The description implies it's for channels but does not state exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adshaa/youtube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server