Skip to main content
Glama
Sign In
Apple Podcasts MCP

Apple Podcasts MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One episode from a feed, in full

get_feed_episode
Read-onlyIdempotent

Find an episode by title, GUID, or episode number and return the full show notes, audio URL, chapters, and transcripts when a listing only shows a truncated description.

Instructions

Find one episode in a show's feed by title, guid or episode number, and return it with its complete show notes, audio URL, chapters and transcripts. Use this when a listing gave a truncated description and the full notes matter, since show notes are where the links, the timestamps and the guest details live.

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": "<show>",
      "episode": "<episode>"
    },
    "name": "get_feed_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
showYesAn RSS feed URL, an Apple Podcasts numeric id, or an Apple Podcasts URL.
limitNoHow many to return, 1-500. How deep into the feed to search.
episodeYesA guid, an episode number, or part of the title. A title match is case-insensitive and takes the first hit, newest first.
storefrontNoOnly used when resolving an Apple id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral detail beyond those annotations by specifying the returned content (complete show notes, audio URL, chapters, transcripts) and explaining why the full notes matter. No contradiction with annotations.

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?

Two sentences, no filler. The first sentence front-loads the action and result; the second adds usage context and supporting rationale. Every phrase 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?

Despite no output schema, the description explicitly states the return contents, and the input schema documents all four parameters with constraints and formats. Combined with safety annotations, this is sufficient for an agent to select and invoke the tool correctly.

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%, so parameters are already fully documented in the schema. The description's mention of 'by title, guid or episode number' restates the episode property description without adding new meaning. Baseline 3 is appropriate because the schema carries the parameter semantics.

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 ('Find one episode') with a clear resource and scope, enumerates lookup keys (title, guid, episode number), and specifies the full payload (show notes, audio URL, chapters, transcripts). It clearly differentiates from listing-like siblings by emphasizing single-episode retrieval with complete content.

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 states when to use: 'Use this when a listing gave a truncated description and the full notes matter.' It gives a concrete decision rule, though it does not name alternative sibling tools or state when not to use it. This is clear context without explicit exclusions.

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