Skip to main content
Glama
wynandw87

YouTube MCP Server

by wynandw87

search_within_channel

Search for videos within a specific YouTube channel by providing the channel URL or handle and a search query.

Instructions

Search for videos within a specific YouTube channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesYouTube channel URL, @handle, or channel ID
queryYesSearch query
max_resultsNoNumber of results (1-50, default: 10)
Behavior1/5

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

No annotations are provided, so the description must bear the full burden. It discloses no behavioral traits such as error handling (e.g., invalid channel URL), result ordering, or whether it searches only recent uploads. This is a significant gap.

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?

The description is a single concise sentence with no wasted words. It could be slightly expanded without becoming verbose, but it is efficiently front-loaded.

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?

With no output schema or annotations, the description does not address return format, error scenarios, or any behavioral details. It is incomplete for an agent to reliably use the 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 parameter descriptions are clear and self-contained. The description adds no additional meaning beyond the schema, so baseline 3 is 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 clearly states the tool searches for videos within a specific YouTube channel, distinguishing it from sibling tools like 'search_videos' which likely search all of YouTube. However, it could be more explicit about the scope (e.g., 'searches only within the channel's uploads').

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 is given on when to use this tool versus alternatives like 'search_videos' or 'get_channel_videos'. The description simply states the function without contextual usage advice.

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/wynandw87/claude-code-youtube-mcp'

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