Skip to main content
Glama
thenavidm

YouTube MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Analyze a channel's performance

analyze_channel
Read-onlyIdempotent

Score recent videos against a channel's median views to reveal true outliers, not just old ones. Returns multiples and flags Shorts for fair comparison.

Instructions

Score a channel's recent videos against its OWN median views, so you can see which ones genuinely outperformed rather than which are simply oldest. Returns a multiple per video, so 3.2x means it did three times that channel's normal numbers. Use this before modelling anyone's content. Shorts are flagged because their views are not comparable to long-form on the same channel.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent videos to score. Default 30.
accountNoWhich connected channel's quota to spend. Only matters when several are connected.
channelYes@handle, channel id, or URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description adds real value beyond them: the return is a per-video multiple, 3.2x means 3x the channel's normal, and Shorts are flagged because their views aren't comparable. It doesn't mention quota cost or pagination, but the substantive semantics are covered.

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 tight sentences: what it does, how to read the output, and when to use it. Front-loaded with the scoring method and no filler.

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?

No output schema exists, yet the description explains the return shape (a multiple per video) and the Shorts caveat, and the input schema fully documents parameters. Nothing material is missing for an agent to call this correctly.

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%, so all three parameters (limit, account, channel) are already documented with types, bounds, and defaults. The description adds no parameter-level detail, so the baseline of 3 applies.

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 (score) and resource (a channel's recent videos) plus the exact method: comparing against the channel's OWN median views. This is distinguishable from siblings like get_channel_analytics or search_videos, which don't normalize per-channel.

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?

"Use this before modelling anyone's content" gives a clear usage context and implicitly excludes raw analytics lookups. It doesn't name an explicit alternative sibling or state when NOT to use it, so it stops short of a 5.

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