Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Search YouTube videos

search_videos
Read-onlyIdempotent

Search public YouTube videos by keyword and filter results by date, order, region, or channel to find relevant content and paginate through matches.

Instructions

Keyword search over public videos with date, order, region and channel filters. Costs ~100 quota units per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoSort order: relevance, date, viewCount, rating, or title.relevance
queryYesSearch keywords.
channel_idNoRestrict results to this channel ID (UC...).
page_tokenNonext_page_token from a previous call, for the next page.
max_resultsNoResults per page, 1-50.
region_codeNoISO 3166-1 alpha-2 country code, e.g. US.
published_afterNoOnly videos published on/after this date (YYYY-MM-DD).
published_beforeNoOnly videos published on/before this date (YYYY-MM-DD).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds a genuinely useful trait not in the annotations: the ~100 quota unit cost per call, which materially affects call strategy. It does not mention pagination behavior, though page_token is documented in the schema.

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?

Two short sentences, zero filler, with the core capability front-loaded and the cost caveat second. Every clause carries information an agent needs.

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?

An output schema exists, so return values need not be explained, and all eight parameters are fully documented in the schema. The description covers scope, filters and cost; only pagination/result-set behavior is left implicit, which is a minor gap 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?

Schema description coverage is 100%, so every parameter is already documented with format details (ISO country code, YYYY-MM-DD dates, 1-50 range). The description only restates the filter categories at a high level and adds no syntax or constraint meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Keyword search over public videos') plus the filter dimensions it supports, which distinguishes it from analytics siblings like get_video_analytics or get_trending_videos. It stops short of naming an alternative search path, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the phrase 'keyword search' signals the discovery use case, and the quota warning hints that it should not be called casually. There is no explicit when-to-use or when-not-to-use guidance relative to siblings such as get_top_videos or list_channel_videos.

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