Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Get revenue (OAuth, monetized channels)

get_revenue
Read-onlyIdempotent

Retrieve estimated YouTube channel revenue, ad revenue, gross revenue, and CPM by date range and currency; returns an unavailable reason if the channel is not monetized or OAuth lacks monetary scope.

Instructions

Estimated revenue, ad revenue, gross revenue and CPM for your channel.

Returns available=false with the reason if the channel is not monetized or the token lacks the monetary scope. 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_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWhen no dates are given: the last N days ending today.
currencyNoISO 4217 currency code, e.g. USD.USD
end_dateNoEnd date YYYY-MM-DD, inclusive.
start_dateNoStart date YYYY-MM-DD, inclusive. Omit both dates to use `days`.
granularityNototal, day, or month.total

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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: the OAuth/monetary-scope requirement and the specific degradation path (available=false plus a reason) for unmonetized channels. That is exactly the kind of beyond-schema disclosure that prevents a failed interpretation of an empty result.

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?

Three short sentences with zero filler: the metric list leads, the failure contract follows, and the auth requirement closes. Nothing is repeated from the schema and no sentence is expendable.

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 return values need not be described, and all five parameters are documented in the schema. The description covers auth prerequisites and the primary failure mode, leaving only minor gaps such as latency, pagination or rate limits on an open-world read.

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 date-window semantics ('Omit both dates to use `days`') and ISO 4217 currency, so the schema carries the parameter burden. The description adds nothing about days, currency, granularity or date ranges, which is acceptable at this coverage level but not value-adding.

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 the specific resource (your channel) and enumerates the metrics returned: estimated revenue, ad revenue, gross revenue and CPM. An agent can tell exactly what question this tool answers. It stops short of naming any sibling or scope boundary, but no sibling in the catalog covers revenue, so ambiguity is low.

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 supplies a hard precondition ('Requires OAuth') and a failure condition (non-monetized channel or missing monetary scope), which tells the agent when the call will not yield data. It gives no explicit when-to-use versus alternative guidance and does not point to auth_status or any other tool for resolving the credential case.

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