Skip to main content
Glama

youtube_research

Research a YouTube topic in one call: run multiple searches, de-duplicate and rank videos by views and recency, then return compact briefs with stats, chapters, transcripts, and comments.

Instructions

Research a topic on YouTube in one call. Runs several searches (your queries, or the topic plus 'explained' and 'review' variants), merges and de-duplicates, ranks by views, recency and how many searches surfaced each video, then returns a compact brief per top video: stats, chapters, description, transcript excerpt (start/middle/end) with top terms, and top comments. Follow up with find_in_video, video_comments(query=...) or watch_video on the most promising ones. n_videos max 8.

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": {
      "topic": "<topic>"
    },
    "name": "youtube_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoauto
sortNorelevance
topicYes
queriesNo
n_videosNo
min_viewsNo
max_minutesNo
min_minutesNo
max_age_daysNo
with_commentsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the mechanics: several searches per call, default query expansion with 'explained'/'review' variants, merging, de-duplication, and a rank function combining views, recency and search-frequency. It also states the hard cap 'n_videos max 8'. It does not warn about latency or cost of fanning out multiple searches, which is the main behavioral omission.

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?

Front-loaded with the purpose and pipeline in the first two sentences, then follow-ups, then a hard constraint. Dense but every clause carries information; only the enumerated return fields section is slightly list-heavy.

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?

An output schema exists, so return values need not be restated, yet the description still summarizes them usefully. However, for a 10-parameter tool with 0% schema coverage and no annotations, it leaves too many knobs (sort vs ranking, with_comments, the time/view bounds) and the cost profile of multi-search fan-out unexplained.

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

Parameters2/5

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

Schema description coverage is 0% across 10 parameters, so the description must compensate and only meaningfully explains `queries` (custom vs default topic-based expansion) and `n_videos` (cap of 8). lang, sort, min_views, max_minutes, min_minutes, max_age_days and with_comments are left entirely to inference, and the unexplained `sort` (default 'relevance') appears to conflict with the described internal views/recency ranking, which is a real ambiguity an agent must resolve.

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?

States a specific verb and resource ('Research a topic on YouTube') and then spells out the actual pipeline: multiple searches, merge, de-duplicate, rank by views/recency/overlap, and return a compact per-video brief. The output shape (stats, chapters, description, transcript excerpt with top terms, top comments) makes it unmistakable versus youtube_search or video_info.

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?

Explicitly positions itself as a one-call alternative to running several searches and names concrete follow-ups (find_in_video, video_comments(query=...), watch_video) with the condition 'on the most promising ones'. It lacks an explicit when-not (e.g., a single known-video lookup should go to video_info), but the intended entry-point role is clear.

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