Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Get top-performing videos (OAuth)

get_top_videos
Read-onlyIdempotent

Retrieve a channel's top videos by views, watch time, likes, comments, shares, subscribers, or engagement for a selected date range, including titles and key metrics.

Instructions

Your channel's top N videos by a metric over a date range, with titles and key metrics.

Requires OAuth; returns an OAUTH_REQUIRED error with setup steps otherwise.

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_top_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWhen no dates are given: the last N days ending today.
limitNoHow many videos, 1-200.
metricNoviews, watch_time, likes, comments, shares, subscribers, or engagement (likes+comments+shares).views
end_dateNoEnd date YYYY-MM-DD, inclusive.
start_dateNoStart date YYYY-MM-DD, inclusive. Omit both dates to use `days`.

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description goes beyond that by disclosing the auth precondition and the concrete failure mode ('returns an OAUTH_REQUIRED error with setup steps otherwise'), which is exactly the kind of context annotations cannot express. Minor gap: it does not state sort direction or behavior when the channel has fewer videos than the limit.

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, front-loaded with the core purpose, then the operational caveat. Nothing is redundant and there is no filler.

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, return values need not be described, and the schema plus annotations cover parameters and safety. The one thing an agent might still want — whether ranking is descending and what happens with fewer videos than limit — is not addressed, keeping it short of a 5.

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 the schema already documents days, limit, metric, and the start/end date pair, including the 'omit both dates to use days' fallback. The description restates the same concepts at a summary level ('top N', 'by a metric', 'date range') without adding format or edge-case detail, so the 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 a specific resource (the authenticated channel's videos), a ranking ('top N ... by a metric'), and a time scope ('over a date range'), plus the payload shape (titles and key metrics). That is enough to separate it from siblings like list_channel_videos or get_video_analytics, though it never names a sibling to draw the boundary 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?

Usage is implied by the phrasing 'top N videos by a metric over a date range' — an agent can infer this is the ranked-summary choice rather than a raw listing. But there is no explicit when-to-use vs. when-not guidance and no alternative tool is named, so the selection decision rests on inference.

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