Skip to main content
Glama
Sign In
YouTube Studio MCP

YouTube Studio MCP

by nelsonrogers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Audience breakdown

get_audience_breakdown
Read-onlyIdempotent

Retrieve audience demographics, geography, device, subscriber status, and content-type breakdowns with view share percentages for channel or video reporting and media-kit charts.

Instructions

Who watches and how: demographics, geography, devices, subscriber vs non-subscriber views, Shorts vs long-form split, playback locations. Rows include readable labels and share_pct of views, ready for media-kit charts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dimension": "<dimension>"
    },
    "name": "get_audience_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows (largest first).
periodNoNamed date range, Studio-style. Rolling ranges end at the latest complete day of data (analytics lag ~2-3 days; dates are US Pacific). Ignored when start_date is set.last_90_days
save_toNoOptional file to also save the rows to (.csv or .json). A bare filename goes in the output directory; absolute paths are allowed.
end_dateNoCustom range end, YYYY-MM-DD (inclusive). Defaults to the latest complete day.
video_idNoLimit to one video (11-character ID, e.g. 'dQw4w9WgXcQ'). Omit for the whole channel.
dimensionYesage / gender / age_gender (viewer %), country, us_state, device (phone, TV, ...), operating_system, subscribed_status (subscribers vs not), content_type (Shorts vs videos vs live), playback_location, sharing_service (where shares go).
start_dateNoCustom range start, YYYY-MM-DD. Overrides `period`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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 fully covered by structured data. The description adds a genuinely useful output-behavior detail: rows carry readable labels and a share_pct of views for chart building. It does not mention data lag or pagination, though the schema's period field does carry the lag note.

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 sentences, front-loaded with the resource scope, with no filler or hedging. The list-style enumeration is slightly dense but every item maps to a real dimension of the tool.

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?

With an output schema present and full schema coverage across seven parameters, the description does not need to explain return values or argument formats. Its remaining gap is routing guidance against sibling analytics tools, which is a minor omission for a clearly scoped read-only report tool.

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% and the dimension enum is documented in the schema itself, so the description adds no parameter meaning beyond structured data. Baseline 3 applies; the description's dimension list merely restates the enum.

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?

The description names the resource concretely ('Who watches and how') and enumerates the axes covered: demographics, geography, devices, subscriber status, Shorts vs long-form, playback locations. That is far more specific than the title 'Audience breakdown'. It does not explicitly contrast itself with get_audience_retention or get_traffic_sources, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the tool for demographic/device/geography splits, but the description never says when to pick it over get_audience_retention or get_traffic_sources, nor does it state prerequisites. No exclusions or alternatives are named.

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

Deploy Server

Other Tools