Skip to main content
Glama

analyze_audience

Read-only

Analyze WHO the signed-in user's YouTube audience is, from their own channel's real data: age and gender of viewers, top countries and where viewers are, and what that means for their content. Call this for ANY question about WHO their viewers are, however phrased: who is my audience; who watches or is watching my channel or videos; who are my viewers or subscribers; who am I reaching or serving; tell me about, describe, or help me understand my audience; what is my audience like; my audience demographics; how old are my viewers or what age range; are my viewers male or female or the gender split; where are my viewers or subscribers from; what countries watch me; my geography or location breakdown. Always the user's own audience, never a competitor's. For HOW people find the channel, whether new people are discovering it, search terms, or reach and the algorithm, use check_discoverability; for what the audience SAYS, wants, or struggles with (from their comments), use read_comments; for what to make next, use evaluate_idea. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.

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": "analyze_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely non-obvious behavior: it reads the real connected channel directly, requires no input, and should be invoked immediately without clarifying questions. It does not discuss result freshness, quota/rate limits, or behavior when no channel is connected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and constraints are front-loaded well, but the middle is an extended trigger-phrase list with heavy overlap ('who is my audience', 'who are my viewers', 'who am I reaching', 'what is my audience like', 'my audience demographics') that repeats in several forms. Trimming the synonymous phrasings would preserve the matching value without the bloat.

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?

For a zero-parameter, read-only tool with no output schema, everything needed to call it correctly is present: what it returns, whose data it reads, when to prefer a sibling, and that no clarification round-trip is required.

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?

Zero parameters, so the baseline is 4. It goes beyond that by stating 'Needs no input: it reads their real connected YouTube channel directly' and warning the agent not to ask for a link or title, which preempts the most likely misuse of an empty 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?

States a specific verb and resource ('analyze WHO the signed-in user's YouTube audience is') and enumerates the exact outputs: age, gender, top countries. It also bounds scope explicitly — 'Always the user's own audience, never a competitor's' — which separates it cleanly from the many siblings.

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

Usage Guidelines5/5

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

Gives explicit when-to-use with a long set of paraphrased triggers, plus named alternatives with the condition that selects them: check_discoverability for HOW people find the channel, read_comments for what the audience says, evaluate_idea for what to make next. It even instructs against a failure mode ('Never ask the creator anything first').

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources