Skip to main content
Glama

YouTube search

youtube_search
Read-onlyIdempotent

Search YouTube: one page of results in YouTube's order (about 20 videos, plus the Shorts and channels YouTube shows with them), each with title, views, length, age, channel and description snippet. Filter by result type, upload date, duration, sort order and features. First page: give query (and any filters). Next pages: give only cursor until next_cursor is null.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder of the results.relevance
typeNoOnly results of one type.all
queryNoThe search terms, or a YouTube search link (its filters are kept).
cursorNoThe next_cursor of the previous answer, exactly as returned, for the next page. Leave it out for the first page; with it, nothing else is needed.
durationNoOnly videos of one length: short (under 4 minutes), medium (4 to 20 minutes), long (over 20 minutes).any
featuresNoFeatures every video must have.
upload_dateNoOnly videos uploaded in the last hour, today, this week, this month or this year.any

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: page size (~20), that results follow YouTube's own order, that Shorts and channels are mixed in, and the cursor-termination rule. It does not mention rate limits or quota, which is the only notable gap.

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 what the tool returns, then filters, then pagination. Every clause carries information an agent needs; nothing is redundant with the title or restates the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description enumerates the returned fields (title, views, length, age, channel, description snippet) and explains pagination termination. For a 7-parameter, all-optional search tool, an agent has everything needed to call it correctly on the first and subsequent pages.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning: it explains that cursor must be passed 'exactly as returned' and that with a cursor 'nothing else is needed,' which clarifies the interaction between cursor and the filter parameters better than the schema alone does.

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 names a specific verb and resource ('Search YouTube') and immediately specifies the scope: one page of results in YouTube's order, roughly 20 videos plus Shorts and channels, with the fields returned. That level of detail lets an agent distinguish this from the entity-lookup siblings (youtube_video, youtube_channel) without opening the schema.

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?

It gives explicit operational guidance for the two modes: 'First page: give query (and any filters)' and 'Next pages: give only cursor until next_cursor is null.' That covers the main decision an agent faces. It does not name an alternative tool or state when not to use search, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources