Skip to main content
Glama
thenavidm

OP3 MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Per-episode download counts for a show's recent episodes

op3_episode_downloads
Read-onlyIdempotent

Fetch per-episode download counts for a show's recent episodes at 1, 3, 7, and 30 days plus all-time, so you can compare episode performance at equal age.

Instructions

Per-episode download counts for a show's recent episodes: downloads in the first 1, 3, 7 and 30 days after publication, plus all-time. Use it to compare how episodes performed at equal age. Note that an empty result is normal for a small or new show, it means OP3's daily rollup has not covered it yet rather than that there is no data.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many episodes to return, newest first.
identifierYesAn OP3 show uuid, a podcast:guid, or the show's RSS feed URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely useful operational context: an empty result means OP3's daily rollup hasn't covered the show yet, not that data is absent. It doesn't discuss latency, rate limits, or refresh cadence.

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?

Three sentences, all front-loaded with the metric list first, then the use case, then the empty-result caveat. Nothing is redundant with the title or schema.

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

Completeness4/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 compensates by naming the return metrics and the empty-result case, which is what an agent most needs. Minor gaps remain around per-episode fields returned and result ordering, though ordering is in the schema.

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% and both parameters (identifier formats, limit default/max, newest-first ordering) are fully documented in the schema. The description adds no syntax or format detail beyond that, 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 verb+resource (per-episode download counts for a show's recent episodes) and enumerates the exact metrics returned (1, 3, 7, 30-day and all-time). This distinguishes it from show-level siblings like op3_show_downloads and the flexible op3_query_downloads without opening either 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?

"Use it to compare how episodes performed at equal age" gives a clear selection criterion, and the empty-result note preempts a common misuse (treating no data as an error). It stops short of naming an explicit alternative for show-level or raw download queries, so no when-not routing.

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