youtube-kit

by eukosh

Overview Schema Source Related Servers Discussions Admin

Python

Local

Search

search

Read-onlyIdempotent

Search YouTube for videos, channels, or playlists.

Instructions

Search YouTube for videos, channels, or playlists.

Quota: 1 of the project's 100 daily search calls per page of up to 50 results.

Input Schema

Name	Required	Description	Default
`kind`	No	What to search for.	video
`limit`	No	Maximum number of results.
`order`	No	Sort order.	relevance
`query`	Yes	Search terms.
`since`	No	Only results published at or after this date or datetime (2026-01-01), or this long ago (90d, 4w).
`channel`	No	Only results from this channel: UC… ID, @handle, or channel URL.
`my_channel`	No	Which of your logged-in channels to work on: UC… ID, @handle or exact title. Omit for the default channel.
`page_token`	No	Continue from a previous result's next_page_token.

Output Schema

Name	Required	Description
`items`	Yes
`total_results`	No	Total reported by YouTube; only an estimate for search.
`next_page_token`	No	Pass as page_token to continue; null at the end.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.1Oct 22, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results. Each page of up to 50 costs 100 quota units."New value: +"Maximum number of results."

First observedv0.1.0Oct 18, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful quota and pagination context: one of the project's 100 daily search calls per page of up to 50 results.

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?

The definition is two sentences with no wasted text. Purpose is front-loaded and the quota constraint follows immediately.

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?

With an output schema, full parameter descriptions, and annotations, the description covers the essential operational caveat around quota and page size. It is complete enough for invocation, though it could say more about when search is preferable to sibling retrieval tools.

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 description coverage is 100%, so the input schema already documents all eight parameters, including enums and defaults. The description adds no parameter-specific semantics beyond the schema baseline.

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

Purpose4/5

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

The description states a specific verb and resource: search YouTube for videos, channels, or playlists. It is clearly distinct from mutation-oriented siblings, but it does not explicitly differentiate itself from retrieval siblings like get_videos, get_channel, or list_playlists.

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 gives no guidance on when to use search versus alternatives such as get_videos or list_playlists. It describes what the tool does, but not the conditions or exclusions for selecting it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.