Apple Podcasts MCP

What this server can reach

status

Read-onlyIdempotent

Check availability of Apple Podcasts sources—public catalog, charts/reviews, local library, and Connect analytics—to identify failures or plan tasks that depend on them.

Instructions

Report which of the four Apple Podcasts sources are available right now: the public catalog, charts and reviews, the local library on this Mac, and Apple Podcasts Connect analytics. Call this first if a tool has failed, or before planning work that depends on the library or on owner analytics. Contacts nothing and costs nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Sep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: 'Contacts nothing and costs nothing,' reassuring the agent that calling it is side-effect-free and cheap. It also clarifies the availability check is current ('right now').

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 with no wasted words. The core reporting function is front-loaded, followed by concrete usage guidance and a cost/contact note. 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 simple, zero-parameter status tool, the description is complete: it states what is reported, when to use it, and what side effects to expect. Even without an output schema, an agent can infer that the result will indicate availability of the four named sources.

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?

The tool has zero parameters and 100% schema description coverage, so there is nothing to explain beyond the baseline. The description's enumeration of the four checked sources adds semantic context about what the status result will relate to.

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 uses a specific verb ('Report') and a precise resource ('which of the four Apple Podcasts sources are available right now'), enumerating each source. It clearly distinguishes itself from the sibling tools by being the only status/diagnostic tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: call first if a tool has failed, or before planning work that depends on the library or owner analytics. This gives an agent a clear decision rule for invoking it.

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