Skip to main content
Glama
Sign In
YouTube Channel MCP

YouTube Channel MCP

by joinhackyard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Best day and time to publish

best_publish_time
Read-only

Compares first-week views of recent uploads by weekday and time of day relative to the channel median, helping identify publish times linked to above-median early performance.

Instructions

Compares first-week views of the channel's recent public uploads by weekday and time of day they were published (in your time zone), relative to the channel median. Uses YouTube Analytics; needs 6+ videos older than a week.

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

Input Schema

NameRequiredDescriptionDefault
sampleNo
channelNoWhich connected channel: channel ID (UC...), @handle or name. Omit to use the default channel.
time_zoneNoIANA time zone, e.g. Asia/Kolkata.UTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds behavior the annotations do not: the data source (YouTube Analytics), the minimum-data prerequisite, and that grouping is done in the caller's time zone rather than the audience's. It does not mention quota cost or whether results are cached, which would be the remaining useful disclosures.

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, no filler, and the operative content (what is compared, against what baseline) comes first with the prerequisite trailing. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must convey the return shape, and it only implies a ranked weekday/time comparison relative to the median without saying what fields or recommendation come back. The prerequisite and data source are well covered, but the missing result description leaves a real gap for a no-output-schema 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 coverage is 67%, so the schema already documents channel and time_zone. The description adds meaning to time_zone by explaining it governs the publish-time grouping, but 'sample' — the parameter with no schema description — is never clarified (is it videos analyzed, weeks, or uploads compared?), and the stated '6+' only partially overlaps its schema minimum.

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?

The description names a specific operation (compares first-week views), a specific population (the channel's recent public uploads), and the grouping dimensions (weekday and time of day published) plus the normalization baseline (channel median). This is clearly distinguishable from the broader get_analytics and the unrelated upload/playlist siblings without opening any schema.

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?

It states a concrete precondition — 'needs 6+ videos older than a week' — which tells the agent when this tool will not produce meaningful results. It does not name an alternative for channels with too little history (e.g. get_analytics) or explicitly say when to prefer this over generic analytics, so it stops short of full routing guidance.

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