Skip to main content
Glama

PopOff Data

by tv.popoff

List tracked seasons

list_shows
Read-only

List every tracked season across all shows, with computed status (upcoming | airing | ended), air dates, reunion date, tracking window (trackingStart/trackingEnd — the days that actually have readings), coverageNote, episode counts, and slugs. Start here to discover what data exists. A franchise can have several seasons listed; for an unqualified question use its most recent season.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoOnly return seasons with this status.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotation readOnlyHint=true already covers safety; the description adds meaning by explaining that status is computed and by detailing the returned fields (tracking window, coverageNote, etc.), giving the agent a clear picture of what the call returns without side effects.

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?

The description is two sentences, front-loads the purpose, and packs useful detail (fields returned, franchise guidance) without redundancy. Every sentence earns its place.

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?

For a read-only listing tool with one optional parameter, the description covers the return payload, the discovery use case, and the franchise nuance. No output schema is needed since the field list is explicitly enumerated.

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?

The schema fully documents the single optional parameter 'status' with an enum and a description ('Only return seasons with this status'), and the tool description adds no extra semantics beyond that. Baseline of 3 is appropriate.

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 states a specific action (list) and resource (tracked seasons) and enumerates the computed fields returned, distinguishing it from siblings like list_episodes (which lists episodes) and get_show (which retrieves a single show). The phrase 'Start here to discover what data exists' establishes its role as a discovery tool.

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?

The description explicitly directs the agent to start here for data discovery and clarifies how to handle multi-season franchises (use the most recent season for unqualified questions). However, it does not explicitly name alternative tools or state when not to use it, leaving some inference to the agent.

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

All PopOff Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct resource or analysis need: cast summaries, single-contestant details, follower time series, follow/unfollow events, follow graph, trend events, and export output are cleanly separated. The descriptions explicitly cross-reference related tools, so an agent should be able to pick the right one without ambiguity.

Naming Consistency5/5

Tool names follow a consistent get_/noun and list_noun pattern, with export_season_csv as the only slight variation—but it still clearly uses verb_noun convention. camelCase is avoided, and duplicate or vague verbs are absent.

Tool Count5/5

Twelve tools is a well-scoped size for a read-only analytics data API. Each tool contributes a meaningful slice of the domain—discovery, show details, cast metrics, raw series, events, graphs, trends, usage, and export—without redundancy or bloat.

Completeness5/5

The surface covers the full read-only workflow: discover shows and seasons, list episodes, inspect contestants and cast, retrieve follower histories, engagement, follow relationships, trend events, and export a citation-ready CSV. No obvious lifecycle dead ends exist since the API is inherently data-access-oriented rather than CRUD.

Resources