Skip to main content
Glama
CreatorDB

creatordb-mcp-server

Official
by CreatorDB

get_youtube_audience

Get YouTube creator's audience demographics: top countries, gender ratio, average age, and age breakdown using channel ID.

Instructions

Get a YouTube creator's audience demographics: audienceLocations (top 6 countries with shares), audienceGender (maleRatio + femaleRatio, binary only), audienceAvgAge (integer), audienceAgeBreakdown (fixed 7 buckets: 13-17/18-24/25-34/35-44/45-54/55-64/65+). When data is missing the endpoint returns the placeholder shape (all 0.0) — treat male+female=0 as missing. Costs 10 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelIdYesYouTube channel ID (the immutable UC… form, e.g. "UCX6OQ3DkcsbYNE6H8uQQuVA"). "@handle", "/c/vanity", and "/user/legacy" URLs are NOT accepted here — resolve them to a UC channelId first.
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses data fields, placeholder shape for missing data, and cost. Lacks rate limits or error conditions but sufficient for core behavior.

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?

Two sentences, front-loaded with main purpose, then details. No fluff, every sentence adds value.

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?

No output schema, so description explains return fields adequately. Missing details on error handling or rate limits, but for a single-parameter tool it's fairly complete.

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 coverage is 100%, but description adds meaning by explaining channelId must be UC form and what forms are not accepted, which is beyond schema description.

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?

Clearly states it gets a YouTube creator's audience demographics and lists specific fields. Distinguishes from siblings by being platform-specific and audience-focused.

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?

Provides context on cost and missing data behavior but does not specify when to use over alternatives like get_tiktok_audience or get_instagram_audience. Implicit context but no explicit guidance.

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/CreatorDB/creatordb-mcp-server'

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