Skip to main content
Glama
BACH-AI-Tools

BACH YouTube API MCP Server

search

Search YouTube videos, playlists, channels, or all content types using filters for duration, features, upload date, and sorting options.

Instructions

Search videos, playlists, channels, or all of them. Quota cost is 2 units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch term
tokenNoPagination token Alternatively, use X-TOKEN in header
geoNoISO 3166-2 country code of the region. Like US (default), GB, CA, IN, etc.
langNoLocale/language for request. Like en, gb, hi, etc
typeNoSearch type filter options: video channel playlist movie show shorts Sorting is not available in shorts
durationNoDuration filter options: short - less than 4 min medium - 4 to 20 min long - more than 20 min
featuresNoVideo Features options: HD subtitles CCommons 3D Live Purchased 4K 360 Location HDR VR180 Multiple features could be joined by ',' For example: HD,subtitles
upload_dateNoUpload Date filter options: hour today week month year
sort_byNoResults Sort options: relevance [default] rating date views
localNoGet localized data, the value must be 1. Works with provided value of geo, if not provided then default is US. Quota Cost +1
X-CACHEBYPASSNoCache bypass, the value must be 1 Quota Cost +1
X-TOKENNoAlternative way to pass Pagination token via headers. This will solve 414, URI too long issue.
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing quota cost (2 units) - important operational behavior. It doesn't mention rate limits, authentication needs, or pagination behavior beyond token parameters, but the quota disclosure is valuable behavioral information.

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?

Two sentences with zero waste - first states purpose, second provides important quota information. Well-structured and appropriately sized for a search tool with many parameters documented elsewhere.

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?

For a complex tool with 12 parameters and no output schema, the description is minimal but covers core purpose and quota cost. Without annotations and with no output schema, it should ideally mention more about response format or pagination, but the quota disclosure helps.

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?

With 100% schema description coverage, the baseline is 3. The description doesn't add any parameter-specific information beyond what's already in the detailed schema descriptions. It mentions quota cost generally but not how specific parameters affect it.

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, playlists, channels, or all of them', providing a specific verb ('search') and resources. It distinguishes from some siblings like 'search_channels_videosplaylists' by being more general, but doesn't explicitly differentiate from all search-related tools.

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?

The description implies usage for general search across multiple content types, but doesn't explicitly state when to use this vs. more specific tools like 'search_channels_videosplaylists' or 'hashtag'. It mentions quota cost which provides some operational context, but lacks explicit guidance on tool selection.

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/BACH-AI-Tools/bachai-yt-api'

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