Skip to main content
Glama

youtube_search

Search YouTube videos by query and filter results by date, channel, duration, definition, order, or safe search, with pagination and automatic fallback when API quota runs out.

Instructions

Search with date/channel/duration filters — port of tube-bridge youtube_search.

Layer 1/2 (Data API, 100 units) → Layer 3 (yt-dlp, 0 units) on exhaustion.
Returns {query, source, total_results, next_page_token, videos[]}.

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": "youtube_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
orderNo
queryYes
channel_idNo
safe_searchNo
video_durationNo
published_afterNo
published_beforeNo
video_definitionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 add real value: it discloses a tiered source strategy (Data API at 100 units, then yt-dlp at 0 units on exhaustion) and names the return envelope, including a `source` discriminator. However, it omits what an agent most needs to know about that fallback — whether the filters are honored when yt-dlp takes over, and whether quota exhaustion silently changes result quality.

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?

Three tight lines with the capability stated first and the return shape last. The 'port of tube-bridge' clause is internal provenance that costs a line without helping an agent decide or invoke, but the rest earns its space.

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 needn't be re-explained, but for a 9-parameter tool with zero schema descriptions the definition is thin. The undocumented optional parameters and the untested interaction between filters and the yt-dlp fallback leave meaningful gaps before an agent can call this confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, so the description must compensate and largely doesn't. 'date/channel/duration filters' loosely maps to published_after, published_before, channel_id, and video_duration, but order, limit, safe_search, video_definition, and accepted value formats are left entirely undocumented.

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?

Names a specific verb (Search) and resource, and flags the filter categories it supports (date/channel/duration). It doesn't explicitly differentiate from the sibling search_videos, so an agent still has to guess which search tool is canonical.

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 statement of when to use this over search_videos or the other search-adjacent siblings. The only situational cue is the implicit hint that date/channel/duration filtering is supported here, which an agent must infer.

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