Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Get channel analytics (OAuth)

get_channel_analytics
Read-onlyIdempotent

Retrieve YouTube channel analytics for a date range, including views, watch time, average view duration, subscriber changes, likes, comments, and shares. Use it to measure performance and report trends.

Instructions

Views, watch time (estimatedMinutesWatched), average view duration, subscribers gained/lost, likes, comments and shares for your channel.

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

Input Schema

NameRequiredDescriptionDefault
daysNoWhen no dates are given: the last N days ending today.
end_dateNoEnd date YYYY-MM-DD, inclusive.
start_dateNoStart date YYYY-MM-DD, inclusive. Omit both dates to use `days`.
granularityNototal (one row), day, or month (start_date must be the 1st) for a time series.total

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new operational context the annotations do not carry: an OAuth prerequisite and the specific OAUTH_REQUIRED error with setup steps returned when auth is missing, which lets an agent anticipate and handle a failure mode. It stops short of noting any rate limits or quota behavior.

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 the metric list followed by the auth caveat; nothing is redundant. The metric enumeration is somewhat long but each item tells the agent what data is available, so it earns its place.

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?

An output schema exists, so the description need not explain return shapes, and the parameter schema fully covers date and granularity semantics. Combined with the auth/error disclosure, the definition gives the agent enough to call the tool correctly; only cross-tool routing guidance is missing.

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 of the four parameters (days, start_date, end_date, granularity) already documented in the schema, including the fallback rule and the month-granularity constraint. The description adds no parameter-level meaning beyond a parenthetical naming the estimatedMinutesWatched return field, so the baseline of 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?

States a specific resource ('channel analytics') and enumerates the exact metrics returned (views, watch time, average view duration, subscribers, likes, comments, shares), so an agent can tell it reports channel-level performance data rather than per-video data. It never names a sibling such as get_video_analytics, so the differentiation is implied by the word 'channel' rather than made explicit.

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 description implies usage through the metrics it reports and the OAuth requirement, but gives no explicit when-to-use guidance, no exclusions, and no routing to alternatives like get_video_analytics or get_channel_report. The agent must infer the choice from sibling names alone.

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