Skip to main content
Glama
l4b4r4b4b4

YouTube MCP Server

by l4b4r4b4b4

search_live_videos

Search for currently live YouTube videos matching your query. Get active broadcasts with details like video ID, title, channel, and thumbnail.

Instructions

Search for currently live YouTube videos.

Searches for videos that are currently streaming live, filtering results
to only active broadcasts. Results are cached for 6 hours.

Args:
    query: Search query (e.g., "gaming live", "news live now").
    max_results: Maximum results to return (1-50, default 5).

Returns:
    List of live video results with video_id, title, description, url,
    thumbnail, channel_title, and published_at.

Example:
    >>> results = search_live_videos("gaming", max_results=10)
    >>> print(results[0]["title"])
    'Live Gaming Stream - Fortnite'

Note:
    - Search costs 100 quota units per request
    - Results cached for 6 hours in youtube.search namespace
    - Use is_live() to check if a specific video is currently live
    - Use get_live_chat_messages() to monitor chat

Caching Behavior:

  • Parameters that accept reference strings can accept a ref_id from a previous tool call

  • Large results return ref_id + preview; use get_cached_result to paginate

  • All responses include ref_id for future reference

Ref input compatibility: Support depends on the tool's input schema/validation. Some strictly typed parameters may reject string ref_ids before resolution.

Full retrieval: Use get_cached_result(ref_id, full=True) to get the complete value.

Preview Size: server default. Override per-call with get_cached_result(ref_id, max_size=...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description fully discloses behavior: results are cached for 6 hours, search costs 100 quota units, and the caching namespace. It also mentions reference ID handling and preview sizes. However, some caching details appear generic and may not be tool-specific.

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

Conciseness3/5

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

The description includes a clear structured intro, Args, Returns, Example, and Note. However, it appends a large block of generic caching behavior text that is not specific to this tool, reducing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, parameters, return format (with output schema present), caching, quota, and related tools. It is complete for a simple tool with two parameters, though some cached behavior text may be extraneous.

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

Parameters4/5

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

Schema description coverage is 0%, but the description's Args section adds meaning: query includes example queries, max_results explains range and default. Both parameters are well-explained beyond the schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search for currently live YouTube videos.' It specifies filtering to active broadcasts, uses a clear verb+resource format, and distinguishes from sibling tools like 'search_videos' by emphasizing live-only results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use the tool, including examples and notes about caching and quota costs. It mentions related tools ('is_live' to check specific videos, 'get_live_chat_messages' for chat monitoring), but does not explicitly state when not to use it or compare directly with 'search_videos'.

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/l4b4r4b4b4/yt-api-mcp'

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