Skip to main content
Glama

videos_searchVideos

Search for YouTube videos using a query and optional filters like channel, date range, subscriber count, and sort order to find specific content.

Instructions

Search for videos on YouTube

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNoSort order for results, such as relevance or date
queryYesSearch query
sortByNoOptional ranking mode such as relevance, indie_priority, subscribers_asc, subscribers_desc, or recent_activity
channelIdNoRestrict results to a specific channel ID
maxResultsNoMaximum number of results to return
creatorOnlyNoOnly include channels heuristically classified as creators
publishedAfterNoOnly include videos published after this ISO 8601 date
uniqueChannelsNoReturn only one matched video per unique channel
publishedBeforeNoOnly include videos published before this ISO 8601 date
channelMaxSubscribersNoMaximum subscriber count for the matched video channel
channelMinSubscribersNoMinimum subscriber count for the matched video channel
channelLastUploadAfterNoOnly include videos whose channel latest upload is after this ISO 8601 date
channelLastUploadBeforeNoOnly include videos whose channel latest upload is before this ISO 8601 date
Behavior2/5

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

There are no annotations, so the description must disclose behavioral traits. It only says 'Search for videos,' omitting any details about rate limits, pagination, return format, or side effects. This is insufficient for an agent to anticipate behavior.

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

Conciseness2/5

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

The description is a single sentence, which is too brief for a tool with 13 parameters. While concise, it is under-specified and does not earn its place; it should include more context.

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?

Given the tool's complexity (13 parameters, no output schema), the description lacks completeness. It does not explain return values, default behaviors, or interaction effects between parameters, leaving the agent underinformed.

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?

The input schema has 100% description coverage, so the schema itself documents each parameter. The tool description adds no additional meaning beyond the schema, making the baseline score of 3 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 a specific verb ('Search') and resource ('videos on YouTube'), making the tool's purpose immediately understandable. However, it lacks any differentiation from potential sibling tools (none provided) and is somewhat generic.

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?

The description provides no guidance on when to use this tool, when not to use it, or any alternatives. With no sibling tools mentioned, the description could at least imply typical search scenarios, but it does not.

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/ZubeidHendricks/youtube-mcp-server'

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