Skip to main content
Glama

max_views_in_channel

Retrieve the maximum view count among a channel's uploads since a specified date to identify breakout videos and assess recent performance.

Instructions

Highest view count among uploads since since_date. New tool.

Layer: Data API. Quota: 1 + 1 per 50 uploads scanned + 1 per 50 videos in
the window (``max_pages`` default caps at 500 uploads).

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": {
      "channel_id": "<channel_id>",
      "since_date": "<since_date>"
    },
    "name": "max_views_in_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_pagesNo
channel_idYes
since_dateYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral context: a concrete quota formula and the fact that max_pages defaults to a 500-upload cap, which warns the agent that results may be truncated. It stops short of saying what happens when the cap is hit or confirming the operation is a read-only scan, but the quota and cap disclosures are substantive.

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 short sentences, front-loaded with the core behavior. The quota sentence is dense and its "1 per 50 videos in the window" phrasing is ambiguous, but nothing is padded or redundant.

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?

An output schema exists, so return values need not be explained, and the metadata fields are reasonably covered. The remaining gap is material for a max-computation tool: the description never states whether the answer is guaranteed over the full window or silently bounded by max_pages, which affects whether the agent can trust the result.

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 0%, so the description must compensate. It meaningfully clarifies max_pages (default caps at 500 uploads scanned) and ties since_date to the aggregation window, but gives no format for since_date (ISO date? relative?) and says nothing about channel_id beyond what the name implies.

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?

States a specific aggregation verb and resource: "Highest view count among uploads since since_date". That is concrete enough to distinguish it from aggregation siblings like avg_duration and from listing siblings like youtube_get_channel_videos, though it never names those alternatives explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternatives. The quota disclosure implicitly informs a cost/benefit decision (a full-channel scan is expensive), but the agent must infer that usage rule rather than being told it.

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