Skip to main content
Glama

youtube_search

Search YouTube videos by query, sort by relevance or date, and filter by view count or duration to find relevant content and retrieve titles, channels, durations, views, and URLs.

Instructions

Search YouTube. sort: 'relevance' or 'date' (newest first). Optional filters: min_views, min_minutes, max_minutes (0 = off). Returns title, channel, duration, views, URL.

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": "youtube_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo
sortNorelevance
queryYes
min_viewsNo
max_minutesNo
min_minutesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the shape of results (title, channel, duration, views, URL) and the meaning of sort and filter values, including the 0 = off convention. It says nothing about quotas, region/language behavior, result caps, or whether the operation is read-only, which are the kind of traits an agent needs for a network-backed search.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action, then parameter semantics, then return shape. The telegraphic style is efficient and nothing is padded, though the fragment form makes the filter sentence slightly dense to parse.

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

Completeness3/5

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

For a six-parameter tool with no annotations, the definition covers filters and return fields adequately, and the output schema handles the response contract. The unexplained `n` parameter and the absence of any behavioral caveats (limits, pagination, regional behavior) leave gaps an agent could hit in practice.

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 0%, so the description must compensate, and it does add real meaning for sort (enum values plus "newest first") and the three numeric filters (including 0 = off). However, the `n` parameter is never explained anywhere — its name and title "N" do not tell an agent it is the result count — and `query` is left entirely implicit, so the coverage is partial.

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 ("Search YouTube") that an agent can immediately map to intent. It does not name or contrast with siblings such as video_info or channel_videos, so the differentiation is implicit rather than explicit.

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 filters and sort options hint at discovery workflows (e.g. newest-first, short videos), but there is no statement of when to pick this over a sibling lookup tool or when it is not appropriate. An agent can infer the context but gets no explicit routing guidance.

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