Skip to main content
Glama
thenavidm

OP3 MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Geography

op3_geography
Read-onlyIdempotent

Report a podcast show's downloads and unique listeners by continent, country, region, metro area, or timezone to compare audience geography and avoid small-market skew.

Instructions

Where a show's downloads come from, at whichever level you ask for: continent, country, region (state or province), metro area, or timezone. Reports downloads and unique listeners side by side for each place, because one enthusiastic listener in a small market otherwise looks like a market. Region and metro are qualified by country, so Illinois and Israel do not merge.

Input Schema

NameRequiredDescriptionDefault
endNoWindow end. Defaults to now.
topNoHow many places to return. The rest are folded into otherCount rather than dropped.
botsNoInclude downloads from known bots. Off by default.
levelNoGranularity. country is the usual answer. region is states and provinces. metro is a US-centric DMA code and is mostly empty outside the US.country
startNoWindow start, e.g. -30d, -8w, 2026-08-01. Defaults to -30d.
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 declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: it reports downloads and unique listeners side by side, and explains that region/metro are qualified by country so same-named places don't merge.

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?

Three sentences, front-loaded with the core purpose, and the market-size rationale for dual metrics earns its place. Slightly conversational but no filler that obscures the operative facts.

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?

No output schema exists, so the description carries the return-value burden and does so by naming the two reported metrics per place. It omits pagination/otherCount handling and default window behavior, but those are already documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds rationale the schema lacks — why two metrics are returned together, and why region/metro results are country-scoped — which helps the agent interpret level choices rather than just enumerate them.

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?

Opens with a specific verb+resource ('Where a show's downloads come from') and enumerates the exact geographic levels available, which cleanly separates it from siblings like op3_audience_summary or op3_device_breakdown. An agent can identify the tool's job without opening the 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?

The description frames the tool as answering at whatever granularity you request and lists the five levels, giving clear context for when each is appropriate. It does not name a sibling alternative or state exclusions, so it stops short of a 5.

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