Skip to main content
Glama

youtube_query

Search YouTube for videos, channels, playlists, comments, and profiles; get latest uploads, topic research with stats, and multi-video creator advice.

Instructions

Query YouTube: search videos/channels/playlists, channel profiles, latest uploads, playlist items, video comments, topic research with stats, or multi-video creator advice. Returns JSON including intent, result items, optional advice{} for goal=advice, next_steps[], and quota_cost. Single-video summaries and verbatim caption lookup use summarize_video and get_transcript.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoUniversal paste target: watch URL, youtu.be link, @handle, channel URL, playlist URL/ID, or plain search text. With intent=auto, Tubask picks the mode.
goalNoShortcut for common jobs: advice (creator themes), latest (uploads), research (topic + stats), comments, playlist, info (one video), search (lightweight). Prefer over intent when unsure.auto
depthNoDetail for goal=advice and per-video analysis: brief ≈ 5 takeaways; detailed ≈ 12 takeaways and longer quotes.brief
orderNoSort order for search/research. date = newest first; viewCount = most viewed; relevance = default keyword ranking.relevance
queryNoSearch keywords for goal=research or goal=search (e.g. 'MCP server tutorial').
intentNoExplicit routing mode when goal is insufficient. Most callers use goal or ref alone.auto
video_refNo11-char video ID or watch URL — for goal=comments or goal=info.
channel_idNoOptional UC... channel ID to scope search/research to one channel.
page_tokenNoOpaque token from next_page_token in a prior response — next page of same query.
channel_refNoYouTube @handle or channel URL — for goal=advice, goal=latest, or channel_info.
max_resultsNoCap on videos, comments, or search hits returned (1–50). goal=advice analyzes up to 8.
result_typeNoSearch target type for goal=search.video
playlist_refNoPlaylist URL or PL... ID — for goal=playlist.
topic_filterNoFor goal=advice: topic to find across a creator's catalog (e.g. 'pricing', 'kubernetes'). Searches the channel, not just recent titles.
comment_orderNoComment sort: relevance (top/liked) or time (newest first).relevance
include_statsNoWhen true, enriches video search/research with views, duration, URL, and is_short. Adds a small YouTube API quota cost on top of search.
exclude_shortsNoWhen true, filters YouTube Shorts and uploads under ~3 min from latest/advice/research videos. Set false for Shorts-first or short-form research.
include_repliesNoInclude reply threads on comments (up to 5 per thread). false reduces payload size.
published_afterNoISO 8601 UTC datetime (2025-01-01T00:00:00Z) — limit research/search to newer uploads.
include_full_descriptionNoReturn full video/channel description instead of a 280-char excerpt.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the return structure ('JSON including intent, result items, optional advice{}... next_steps[], and quota_cost') and mentions quota cost, which is a useful behavioral trait. It could go further by noting rate limits or error behavior, but the current disclosure is solid for a read-only query tool.

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?

The description is two sentences and front-loaded with 'Query YouTube.' The first sentence is a comprehensive list of capabilities; the second covers return format and sibling delegation. It is slightly list-heavy but each item earns its place, and it avoids unnecessary repetition of schema details.

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?

For a complex 20-parameter tool with no output schema, the description provides a strong high-level overview of all capabilities, output fields (intent, result items, advice, next_steps, quota_cost), and sibling alternatives. It does not explain every scenario, but combined with the fully documented schema, it is sufficiently complete for an agent to invoke correctly.

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 provides 100% description coverage of all 20 parameters, including enums and defaults, so the baseline is 3. The description adds minimal parameter-specific context beyond mentioning goal=advice and advice{} in the return. It does not enrich parameter meanings further, so a 3 is appropriate.

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 uses a specific verb ('Query') and enumerates distinct resource types and operations: search videos/channels/playlists, channel profiles, latest uploads, playlist items, video comments, topic research, and creator advice. It clearly distinguishes from siblings summarize_video and get_transcript by delegating single-video summaries and caption lookup to those tools.

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

Usage Guidelines5/5

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

The description explicitly names alternatives: 'Single-video summaries and verbatim caption lookup use summarize_video and get_transcript.' It also outlines the main modes via goal examples (advice, latest, research, comments, playlist, info, search) and states the return format, giving the agent enough context to choose this tool for broad YouTube queries.

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/Amorizz/tubask-mcp'

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