Skip to main content
Glama

Get series performance

get_series_performance
Read-onlyIdempotent

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. Only your own videos; views come from daily YouTube snapshots; audience retention is not available. Requires the "video:read" scope. 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": "get_series_performance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (which already cover read-only, idempotent, non-destructive, closed-world), the description discloses data provenance ('views come from daily YouTube snapshots'), an explicit data limitation ('audience retention is not available'), an auth requirement ('Requires the "video:read" scope'), and cost ('Free'). These are exactly the behavioral facts an agent needs and cannot get from the structured fields.

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?

Information is front-loaded: what it returns, why to use it, then caveats and auth. Every clause carries substance, though the trailing 'Free, read-only' partly restates the annotations, which is minor redundancy in an otherwise dense and efficient description.

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 full burden of describing returns, and it does so thoroughly, including the outlierScore formula and the comparative 7-day metric. Combined with the disclosed limitations and scope, an agent has everything needed to call and interpret this 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 100%, so both parameters (days, seriesId) are already fully documented, including the 30-day default and the 'omit for every series' behavior. The description adds only the aggregate-per-series framing and nothing about parameter units or interaction (e.g., whether days filters videos or the 7-day window), 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?

The description opens with a specific verb and resource ('How YOUR OWN posted YouTube Shorts performed, per series') and then enumerates exactly what is returned: videos posted/measured, total/median/mean views, top/bottom 3 with outlierScore, and a 7-day vs prior-7-day delta. This clearly separates it from the single-video 'get_video' and the enumeration-only 'list_series'.

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 gives clear decision-making context ('Use it to decide what to make next') and states a scope constraint ('Only your own videos'), which tells the agent when this tool is the right one. It stops short of explicitly routing the agent to an alternative for other cases (e.g., single-video stats), so it is strong but not exhaustive.

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