Skip to main content
Glama

youtube_search

Search YouTube for videos by query, with options to filter by type (video, channel, playlist) and sort by relevance, date, view count, or rating. Returns title, description, channel name, thumbnail, and video URL for tutorials, demos, and educational content.

Instructions

Search YouTube for videos. Returns title, description, channel name, thumbnail URL, and video URL. Great for tutorials, demos, and educational content. Requires YOUTUBE_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query
per_pageNoResults per page
orderNoSort orderrelevance
typeNoResult type filtervideo
Behavior3/5

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

No annotations are provided, so description bears full burden. It states it requires YOUTUBE_API_KEY, which is good. However, it doesn't mention rate limits, pagination, or output format details. Returns fields are noted but no details on behavior beyond that.

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 sentences, front-loaded with purpose, then returns, then context. No wasted words.

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?

Tool has 4 params, no output schema, no annotations. Description covers purpose, returns, and a requirement (API key). It could mention pagination but overall sufficient for a search tool.

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?

All 4 parameters are described in the schema (100% coverage). The description adds no additional semantics beyond listing returns. However, the schema already provides enums and defaults, so additional description is not critical. Baseline 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 clearly states 'Search YouTube for videos' and lists the return fields, distinguishing it from sibling tools. It specifies that it's for videos, which is a specific resource.

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?

The description mentions it's 'Great for tutorials, demos, and educational content', providing context for when to use. However, it does not explicitly say when not to use or name alternative 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/bartonguestier1725-collab/scout-mcp'

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