Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

by tuitamogamer-gpt
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Revenue Analytics

youtube_revenue
Read-onlyIdempotent

Get estimated revenue, CPM, monetized playbacks, and ad impressions for your YouTube channel. Optionally break down by day or month.

Instructions

Retrieve revenue and monetization metrics for the authenticated channel, including estimated revenue, CPM, monetized playbacks, and ad impressions. Optionally break down by day or month.

IMPORTANT: This tool requires:

  1. The yt-analytics-monetary.readonly OAuth scope (included if you ran npm run auth with the default SCOPES).

  2. The channel must be enrolled in the YouTube Partner Program (monetized). If either condition is not met, the API returns HTTP 403.

Args:

  • 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), "day", or "month".

  • currency (optional): ISO 4217 three-letter currency code, e.g. "EUR". Defaults to "USD".

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

Returns (JSON shape):

{
  "columns": ["estimatedRevenue", "estimatedAdRevenue", "grossRevenue", "cpm",
               "playbackBasedCpm", "monetizedPlaybacks", "adImpressions"],
  "rows": [[1234.56, 1100.00, 1300.00, 5.20, 4.80, 240000, 1500000]]
}

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

Examples:

  • "How much revenue did I make this month?" → pass appropriate date range.

  • "Daily revenue breakdown in EUR" → dimension: "day", currency: "EUR".

Errors:

  • 403: channel is not in the YouTube Partner Program, the yt-analytics-monetary.readonly scope was not granted, or YouTube Partner status is missing. Re-run npm run auth and ensure your channel is monetized.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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, "month" for per-month rows.none
currencyNoISO 4217 three-letter currency code for revenue figures, e.g. "USD" (default), "EUR", "GBP".
response_formatNoOutput format: "markdown" (default) for a human-readable table, "json" for the structured payload.markdown

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds authentication prerequisites, YPP requirement, error conditions, default date ranges, and effect of dimension parameter on output. No contradictions; adds substantial behavioral context.

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 clear sections: introduction, important notes, args, returns, examples, errors. Every sentence provides value; no redundancy. It is detailed yet concise, and front-loaded with key purpose and requirements.

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 no output schema, the description provides the JSON shape with columns and rows, explains dimension effects, covers errors, and includes examples. All necessary information for an AI agent to use the tool correctly is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description enriches each parameter with defaults, allowed values, format requirements (e.g., ISO 4217 for currency), and examples. It clarifies the dimension parameter behavior and response_format options, adding beyond the 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 explicitly states it retrieves revenue and monetization metrics for the authenticated channel, listing specific metrics like estimated revenue, CPM, etc. It clearly identifies the resource (channel) and the action (retrieve), making the purpose unambiguous.

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?

The description includes critical usage requirements: OAuth scope and YPP enrollment, with a clear note about 403 errors. It provides examples and default behaviors. However, it lacks explicit comparison to sibling tools like 'youtube_video_performance' or 'youtube_run_analytics_query', which could help agents choose the right tool.

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