Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Get trending videos

get_trending_videos
Read-onlyIdempotent

Retrieve trending YouTube videos by country and optional category, including view and engagement stats, to identify what audiences are watching now.

Instructions

YouTube's most-popular videos in a country right now, optionally in one category, with stats. 1 quota unit.

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

Input Schema

NameRequiredDescriptionDefault
page_tokenNonext_page_token from a previous call, for the next page.
category_idNoVideo category ID, e.g. 26 Howto & Style, 22 People & Blogs, 19 Travel & Events. Omit for all.
max_resultsNoItems per page, 1-50.
region_codeNoISO 3166-1 alpha-2 country code, e.g. CA.US

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 behavior, so the safety profile is covered. The description adds genuinely new context in the form of the one-quota-unit cost per call, which matters for a metered API. It stops short of noting pagination behavior or that results are region-restricted to what the API returns, keeping it below a 5.

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?

A single front-loaded sentence with the resource first, then scope modifiers, then the quota cost. There is no filler and nothing an agent would need to re-read.

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?

With an output schema present, the description does not need to explain return values, and all four parameters are separately documented. The quota cost and region/category scoping round it out; only the absence of sibling disambiguation from get_top_videos keeps it from being fully complete.

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%, with each parameter documented in the schema itself (page token, category ID examples, 1-50 max results, ISO region code). The description only mirrors this by saying 'in a country' and 'optionally in one category', adding no format or default guidance beyond the schema. 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?

The description names the specific resource (YouTube's most-popular videos), the scope (a country, right now, optionally one category), and adds that stats are returned. It is clear to an agent what the tool returns, but it never distinguishes itself from the sibling get_top_videos, leaving a plausible ambiguity.

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 implied by 'right now' (current trending rather than historical top videos), and the '1 quota unit' note gives cost context for deciding whether to call. However, there is no explicit when-to-use guidance, no exclusion, and no pointer to get_top_videos or search_videos as alternatives.

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