Skip to main content
Glama

Get series performance

autoshort_get_series_performance
Read-onlyIdempotent

Compare your posted YouTube Shorts series by views, median performance, top and bottom videos, and recent view growth to decide which formats to repeat or drop.

Instructions

How YOUR OWN posted YouTube Shorts performed, per series: videos posted/measured, total/median/mean views, top 3 and bottom 3 videos (with outlierScore = views / series median), and views gained in the last 7 days vs the 7 days before. Use it to decide what to make next: repeat the formats of the best videos, drop the worst. Only your own videos; views come from daily YouTube snapshots; audience retention is not available. Free, read-only.

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

Input Schema

NameRequiredDescriptionDefault
daysNoOnly videos created in the last N days (default 30).
seriesIdNoOne series id (from autoshort_list_series). Omit for every series with posted videos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, but the description adds provenance and constraints they cannot carry: views derive from daily YouTube snapshots, audience retention is unavailable, and only the caller's own videos are covered. It also flags 'Free', which matters for planning. That is exactly the extra context the annotations leave out.

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?

The core purpose and scope are front-loaded, and the metric enumeration is dense but each item is information the agent needs. The outlierScore definition is folded inline efficiently. Slightly heavy as a single run-on sentence, but 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?

With no output schema, the description carries the return-value burden itself and does so: it lists the aggregate stats, the top/bottom 3 selection, the outlierScore formula, and the 7-day window comparison. Combined with the stated data source and known limitation, an agent can call this and interpret results without guessing.

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 both parameters (days, seriesId) are already fully documented, including the default and the pointer to autoshort_list_series. The description adds only indirect meaning via 'per series' and the 7-day comparison framing, so the baseline 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 resource and scope: 'How YOUR OWN posted YouTube Shorts performed, per series', then enumerates exactly what is returned (posted/measured counts, total/median/mean views, top/bottom 3, 7-day deltas). The 'Only your own videos' clause and the per-series framing separate it cleanly from single-video or account-wide siblings.

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?

Gives an explicit decision context: 'Use it to decide what to make next: repeat the formats of the best videos, drop the worst.' That is real when-to-use guidance, not just a restatement. It stops short of naming an alternative for related questions (e.g., per-video or account-wide stats) or stating when-not to call it.

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