Open Podcast Prefix Project (OP3) MCP Server

op3_top_apps

Identify the top podcast apps and players used by listeners to download a show, with download counts and percentage share, over the last three months.

Instructions

Get the top podcast apps and players downloading a show, from OP3, over the last three calendar months. Returns each app with its download count and percent share. Answers 'what apps do my listeners use'. Needs a show UUID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "show_uuid": "<show_uuid>"
    },
    "name": "op3_top_apps"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max apps to return, ranked by downloads (default 10).
`show_uuid`	Yes	OP3 show UUID (32 hex chars).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 25, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the return shape (download count and percent share), time range (last three months), and prerequisite (UUID). It does not mention rate limits, auth needs, or other behaviors, which would be helpful.

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 concise sentences with no fluff. It front-loads the main action and time range, then adds return details and prerequisite. Every sentence serves a purpose.

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?

Given the low complexity (2 params, no output schema), the description is complete. It explains what the tool does, what it returns, the time range, and the required parameter. An agent can use it correctly without additional context.

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% with good parameter descriptions. The description adds value by explaining the time range and return shape, which goes beyond the schema. It compensates well for the lack of output schema.

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 clearly states the verb 'Get', the resource 'top podcast apps and players', and the scope 'over the last three calendar months'. It also answers the question 'what apps do my listeners use', distinguishing it from sibling tools like op3_top_countries.

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 specifies the prerequisite 'Needs a show UUID' and implies usage for app breakdown. However, it does not explicitly mention when not to use it or provide alternatives, though the sibling list gives context.

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

Deploy Server