Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Build a channel report (OAuth)

get_channel_report
Read-onlyIdempotent

Generates a shareable YouTube channel performance report covering totals, period-over-period change, net subscribers, top videos, audience highlights, and top searches.

Instructions

A ready-made performance report: totals and % change vs the previous period, net subscribers, top videos, audience highlights and top YouTube searches.

Includes the same report rendered as Markdown under markdown, ready to share. Requires OAuth.

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

Input Schema

NameRequiredDescriptionDefault
top_nNoTop videos to include, each with its main traffic source.
periodNolast_7_days, last_28_days, last_week (previous Mon-Sun) or last_month. Ignored when dates are given.last_week
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.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real context: it requires OAuth and returns a Markdown rendering under `markdown`, which is operationally useful and not derivable from the annotations.

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?

Two short sentences, front-loaded with what the report contains before the Markdown/OAuth note. The content enumeration is dense but each item earns its place by telling the agent what it will get.

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 re-explained, and the OAuth prerequisite is disclosed. What's missing is any routing guidance relative to the many sibling analytics tools, which matters for a composite report that overlaps their scope.

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%, including period formats and the note that dates override `period`; the description adds nothing about top_n, period, or date handling. Baseline 3 applies since the schema carries the full parameter burden.

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?

Names a concrete deliverable (a performance report) and enumerates its sections: totals with % change vs previous period, net subscribers, top videos, audience highlights, top YouTube searches. That content list implicitly differentiates it from narrower siblings like get_channel_analytics or get_top_videos, though it never says so directly.

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 phrase 'ready-made performance report' hints that this is a bundle to use instead of assembling individual analytics calls, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer the tradeoff against get_channel_analytics, get_audience_insights, and get_top_videos.

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