Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_trending

Read-only

Lists trending videos by region, optionally filtered by video category, so you can discover what audiences are watching.

Instructions

List the most popular videos for a region (default US), optionally in one video category. 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": "youtube_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageTokenNoPage token from the nextPageToken of a previous response, to fetch the next page.
maxResultsNoMaximum number of items to return, 1-50; omit to use the tool default.
regionCodeNoTwo-letter ISO 3166-1 region code, e.g. US.
videoCategoryIdNoNumeric video category ID from youtube_list_video_categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.1
    • addedInput schema / properties / maxResults / description
      Added value: +"Maximum number of items to return, 1-50; omit to use the tool default."
    • addedInput schema / properties / pageToken / description
      Added value: +"Page token from the nextPageToken of a previous response, to fetch the next page."
    • addedInput schema / properties / regionCode / description
      Added value: +"Two-letter ISO 3166-1 region code, e.g. US."
    • addedInput schema / properties / videoCategoryId / description
      Added value: +"Numeric video category ID from youtube_list_video_categories."
  2. Addedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds a genuinely useful behavioral fact not present in structured data: the call costs 1 quota unit, which lets an agent budget calls. It does not describe result fields, but with no output schema and a simple list operation that gap is minor.

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, no filler, with the primary action and scope front-loaded and the quota cost trailing as a secondary note. Every clause carries information.

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?

Covers action, scope, default, optional filter, and cost for a four-parameter, fully-optional, read-only list tool. Pagination and return shape are documented in the schema fields, so their absence from the description is acceptable.

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 baseline is 3. The description still adds meaning beyond the schema by stating that regionCode defaults to US and that videoCategoryId is optional and singular, which the schema does not say (it only gives 'e.g. US').

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: list the most popular videos for a region, optionally within one category. That distinguishes it in intent from youtube_search and youtube_consumption_trends, though it never names a sibling explicitly.

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?

The context is implied well enough (trending/popular browsing, not searching), and the default region is a helpful usage cue. However, it never says when to prefer it over youtube_search or youtube_consumption_trends, nor any exclusion or prerequisite.

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

Deploy Server

Other Tools