Skip to main content
Glama
mrsknetwork

YouTube MCP

by mrsknetwork

search_content

Read-only

Search YouTube for videos, channels, or playlists using keyword queries. Filter results by content type, duration, quality, region, and publish date. Supports pagination.

Instructions

Search YouTube for videos, channels, or playlists. Returns items[].id (videoId/channelId/playlistId) and items[].snippet (title, description, thumbnails, channelTitle, publishedAt). Use content_type to filter by resource type. Use page_token from a previous response to paginate additional pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
search_queryYesSearch query
max_resultsNoDefault is 5. Max is 50.
content_typeNoComma-separated list (e.g., 'video,channel,playlist')
orderNoSort order for results. Use 'date' for newest first, 'viewCount' for most watched, 'rating' for top rated.
published_afterNoRFC 3339 datetime (e.g., '2024-01-01T00:00:00Z'). Only return results published after this time.
published_beforeNoRFC 3339 datetime (e.g., '2024-12-31T23:59:59Z'). Only return results published before this time.
video_durationNoFilter by video duration — short (<4 min), medium (4-20 min), long (>20 min). Only applies when content_type includes 'video'.
video_definitionNoFilter by video quality — 'hd' or 'standard'. Only applies when content_type includes 'video'.
region_codeNoISO 3166-1 alpha-2 country code (e.g., 'US', 'GB', 'IN') to geo-restrict search results.
page_tokenNoToken from a previous response to fetch the next page of results.
Behavior4/5

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

Discloses return structure and pagination behavior. Annotations already provided readOnlyHint and openWorldHint; description adds context on response format without contradicting.

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

Conciseness5/5

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

Three concise sentences front-load essential information (purpose, return structure, key usage) with no redundant or confusing text.

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 return structure, filtering, pagination, and key parameters. With no output schema, description provides sufficient context for an agent to use the tool correctly, though some nuances (e.g., order parameter implications) are left to the schema.

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?

Schema coverage is 100% so baseline is 3. Description adds minor value by clarifying that content_type is a comma-separated list and explaining page_token usage, but does not significantly enhance beyond schema.

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?

Description states specific verb 'Search YouTube' for resources 'videos, channels, or playlists' and details return structure (items[].id, items[].snippet). Distinct from sibling tools like get_video_metadata which fetch specific resources.

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 clear guidance on using content_type to filter and page_token for pagination. Lacks explicit alternatives or when-not-to-use compared to sibling search/list tools.

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/mrsknetwork/ytmcp'

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