Skip to main content
Glama
iamkw0n
by iamkw0n

search_videos

Search YouTube videos by keyword with filters for duration, region, upload date, and sorting order. No API key required.

Instructions

키워드로 YouTube 동영상을 검색합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes검색 키워드
maxResultsNo최대 결과 수
orderNo정렬 기준relevance
publishedAfterNo이후 게시된 동영상만 (ISO 8601, 예: 2025-01-01T00:00:00Z)
publishedBeforeNo이전 게시된 동영상만 (ISO 8601)
regionCodeNo지역 코드 (예: KR, US)
videoDurationNo길이 필터 (short: 4분 미만, medium: 4~20분, long: 20분 이상)
pageTokenNo다음 페이지 토큰 (이전 응답의 pageToken)
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only says 'searches YouTube videos by keyword' without mentioning rate limits, authentication needs, output format, or any side effects.

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 is a single sentence, which is concise but lacks substantive detail to be efficient; it does not prioritize key information.

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?

With 8 parameters, no output schema, and no annotations, the description is incomplete. It fails to specify typical outputs, pagination, or filtering behavior beyond schema hints.

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 has 100% parameter description coverage, so the baseline is 3. The description does not add additional semantic meaning beyond the schema's own descriptions.

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 explicitly states it searches YouTube videos by keyword, distinguishing it from sibling tools like search_channels (for channels) and get_videos (for specific videos by ID).

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it specify any prerequisites, contexts, or exclusions.

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/iamkw0n/youtube-mcp'

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