Skip to main content
Glama
thenavidm

OP3 MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

A show's headline download numbers

op3_show_downloads
Read-onlyIdempotent

Retrieve a podcast show's headline download numbers: last 30 days, a week-by-week breakdown over four weeks, and the weekly average, excluding bots.

Instructions

A show's headline download numbers: downloads in the last 30 days, the week-by-week breakdown over the last four weeks, and the weekly average. This is the fast answer to 'how many downloads does my show get' and should be preferred over the raw query tools whenever it can answer the question. Excludes bots. Updated once a day.

Input Schema

NameRequiredDescriptionDefault
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.3/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive semantics, so the bar is lower; the description adds genuinely new behavior: bot exclusion and once-a-day refresh, both of which affect how an agent should interpret and trust the numbers. It does not cover pagination or error behavior, but for an aggregate read this is solid.

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 tight sentences: what it returns first, then the routing rule, then the behavioral caveats. Every sentence carries information and nothing is padded.

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?

There is no output schema, so the description must describe the return payload, and it does so concretely (last 30 days, four-week weekly breakdown, weekly average). Combined with annotations and a fully documented parameter, an agent has everything needed to call and interpret it.

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 the single identifier parameter is fully documented (uuid, podcast:guid, or RSS URL) in the schema. The description adds no further parameter meaning, 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 (a show's headline download numbers) and enumerates exactly what is returned: 30-day downloads, four-week week-by-week breakdown, and weekly average. This clearly distinguishes it from siblings like op3_episode_downloads, op3_download_trend, and op3_query_downloads.

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?

Explicitly says it 'should be preferred over the raw query tools whenever it can answer the question,' which gives a positive selection rule and names the alternative category. It stops short of naming specific sibling tools or stating when this tool is NOT sufficient (e.g. custom date ranges).

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