Skip to main content
Glama
mcp-public-intel

mcp-public-intel

by pecopeko

podcast_rss_transcripts

Resolve a podcast from a search query, Apple Podcasts ID/URL, or RSS feed to extract show metadata, owner contact emails, and Podcasting 2.0 transcripts without an API key.

Instructions

Resolve a podcast by Apple iTunes search query, Apple Podcast ID/URL, or direct RSS URL to extract show metadata, host contact emails (itunes:owner), and Podcasting 2.0 VTT/SRT/JSON transcripts. Zero API key required.

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": {
      "query_or_rss_url": "<query_or_rss_url>"
    },
    "name": "podcast_rss_transcripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of episodes to return (1-20, default 5).
query_or_rss_urlYesPodcast search query, Apple Podcasts URL/ID, or direct public RSS feed URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations present the description carries the full burden, and it does disclose the key behavioral facts: no API key required, read-only extraction, that host emails come from the <itunes:owner> tag, and which transcript formats exist (VTT/SRT/JSON). It does not cover rate limits, what happens when a show has no Podcasting 2.0 transcript tags, or whether partial results are returned, so it is strong but not complete.

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 tight sentences with zero filler; the accepted input forms and the returned artifacts are front-loaded, and the 'Zero API key required' note is a useful closing constraint rather than padding.

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?

For a two-parameter tool with no output schema, the description does the necessary work by naming what comes back (metadata, owner emails, transcripts) and their formats. The only gap is failure/empty-result behavior, which matters here because transcript availability varies by feed.

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 coverage is 100% and the schema already spells out all three input formats for query_or_rss_url, so the description largely restates it rather than adding format, quoting, or ID-normalization rules. The limit parameter is not mentioned in the description at all, leaving its interaction with transcript retrieval entirely to the 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 names a specific verb chain (resolve → extract) and a specific resource (podcast show), and enumerates the concrete outputs: show metadata, host contact emails from <itunes:owner>, and Podcasting 2.0 VTT/SRT/JSON transcripts. None of the listed siblings operate on podcasts, so the domain boundary is unambiguous.

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?

It clearly states the three accepted input modes (Apple iTunes search query, Apple Podcast ID/URL, or direct RSS URL), which is the practical usage guidance an agent needs to pick an argument form. It stops short of explicit exclusions or when-not-to-use conditions, and gives no hint about what to do when a feed lacks transcripts.

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