Skip to main content
Glama
l4b4r4b4b4

YouTube MCP Server

by l4b4r4b4b4
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

is_live

Check if a YouTube video is currently broadcasting live. Gets live status, viewer count, and scheduled or actual start time.

Instructions

Check if a YouTube video is currently live.

Queries the YouTube Data API to determine if a video is currently
broadcasting live. Returns live status with viewer count and timing information.
Cached for 30 seconds since live status changes quickly.

Args:
    video_id: YouTube video ID to check (e.g., "dQw4w9WgXcQ").

Returns:
    Dictionary with:
    - video_id: YouTube video ID
    - is_live: Boolean indicating if video is currently live
    - viewer_count: Current concurrent viewers (None if not live)
    - scheduled_start_time: ISO 8601 scheduled start time (None if not scheduled)
    - actual_start_time: ISO 8601 actual start time (None if not started)
    - active_live_chat_id: Live chat ID (None if no chat or not live)

Example:
    >>> status = is_live("dQw4w9WgXcQ")
    >>> if status["is_live"]:
    ...     print(f"Live now with {status['viewer_count']} viewers!")

Note:
    - Costs 1 quota unit per request
    - Cached for 30 seconds in youtube.api namespace
    - Use search_live_videos() to find live streams

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
video_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Discloses caching (30 seconds), quota cost (1 unit), and return fields. As a read-only check, no side effects are implied. Without annotations, this is fairly transparent, though could explicitly state read-only.

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?

Core content is good, but appended generic caching/ref_id boilerplate adds unnecessary length. Could be more concise by removing system-wide notes specific to the server context.

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?

Covers purpose, parameter, return format, example, caching, and alternative tool. Missing error handling scenarios and prerequisites (e.g., API key), but for a simple check, this is largely complete.

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

Parameters5/5

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

Adds significant meaning beyond schema: provides description and example for video_id ('YouTube video ID to check, e.g., dQw4w9WgXcQ'). This fully compensates for the 0% schema coverage.

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 it checks if a YouTube video is currently live, uses specific verb and resource, and distinguishes from sibling tools like search_live_videos which find live streams.

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?

Provides context for when to use (checking a specific video's live status) and mentions alternative search_live_videos(). Lacks explicit when-not-to-use, but overall guidance is clear.

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