Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

by tuitamogamer-gpt
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Video Performance Analytics

youtube_video_performance
Read-onlyIdempotent

Retrieve detailed analytics for any YouTube video including views, watch time, retention, subscriber impact, and engagement. Optionally get a day-by-day breakdown.

Instructions

Retrieve detailed analytics for a single YouTube video, including views, watch time, retention, subscriber impact, engagement, and more. Optionally break down by day.

Args:

  • videoId (required): The YouTube video ID, e.g. "dQw4w9WgXcQ".

  • startDate (optional): Inclusive start date in YYYY-MM-DD format. Defaults to 28 days ago.

  • endDate (optional): Inclusive end date in YYYY-MM-DD format. Defaults to today.

  • dimension (optional): "none" (default, aggregate) or "day" (per-day breakdown).

  • response_format (optional): "markdown" (default) or "json".

Returns (JSON shape):

{
  "columns": ["views", "estimatedMinutesWatched", "averageViewDuration", "averageViewPercentage",
               "subscribersGained", "subscribersLost", "likes", "dislikes", "comments", "shares"],
  "rows": [[5000, 12000, 144, 55.3, 30, 2, 200, 5, 40, 15]]
}

When dimension is "day", the first column is the date string.

Examples:

  • "How did video dQw4w9WgXcQ perform last month?" → videoId: "dQw4w9WgXcQ" with date args.

  • "Day-by-day views for my latest video" → videoId: "...", dimension: "day".

Errors:

  • 400: invalid video ID format or unsupported metric/dimension pair.

  • 403: insufficient scope — re-run npm run auth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoIdYesYouTube video ID to analyze, e.g. "dQw4w9WgXcQ".
startDateNoInclusive start date in YYYY-MM-DD format. Defaults to 28 days ago.
endDateNoInclusive end date in YYYY-MM-DD format. Defaults to today.
dimensionNoTime grouping: "none" (default) for aggregate totals, "day" for per-day rows.none
response_formatNoOutput format: "markdown" (default) for a human-readable table, "json" for the structured payload.markdown

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds error behavior (400, 403 with re-auth suggestion) and return format details, which are not in annotations. No contradictions with annotations.

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?

The description is well-structured with sections (Args, Returns, Examples, Errors), front-loads the purpose, and every sentence adds value without redundancy. It is appropriately sized for a 5-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (5 parameters, 1 required, enums) and no output schema, the description provides thorough context: parameter defaults, return shape, examples, and error handling. Only minor omission is explicit permission scope details, but 'insufficient scope' error covers it.

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 description coverage is 100%, but the description enriches parameters with examples (e.g., videoId 'dQw4w9WgXcQ'), defaults, and format constraints. The included return JSON shape clarifies expected output beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Retrieve') and resource ('detailed analytics for a single YouTube video'), clearly stating the tool's function. It lists specific metrics (views, watch time, etc.) and distinguishes from siblings like youtube_channel_summary by targeting a single video.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Examples show concrete use cases ('How did video dQw4w9WgXcQ perform last month?'), and the description implies usage through example inputs. However, it does not explicitly state when not to use this tool versus alternatives, such as channel-level or custom analytics queries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tuitamogamer-gpt/youtube-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server