Skip to main content
Glama
paulet4a-commits

webdatatools-social-mcp

by paulet4a-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

podcast_lookup

Search or resolve Apple Podcasts by ID, URL, RSS feed, or search term, returning podcast metadata and episode lists from each show's RSS feed.

Instructions

Apple Podcasts lookup by id, URL, RSS feed or search term — podcast metadata (artwork, genres, episode count) plus the full episode list from the show's own RSS feed, one row per podcast or episode. Billed to your own Apify account: ~$0.001 per episode (Apify free-plan price, lower on paid plans).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoStorefront country — Enter the two-letter country code of the Apple Podcasts storefront to search and look up ids in, e.g. us, gb, de. Only affects the iTunes lookup/search step — an RSS feed URL entry ignores this.us
podcastsYesPodcasts — Enter one podcast per row: an Apple Podcasts id (1200361736), an Apple Podcasts URL (https://podcasts.apple.com/us/podcast/the-daily/id1200361736), an RSS feed URL (https://feeds.simplecast.com/Sl5CSM3S), or a search term prefixed with search: (search:true crime, which returns up to searchLimit podcasts). Example: ["1200361736"].
outputModeNoOutput mode — Choose podcasts for one row per podcast (metadata only), or episodes for one row per episode (podcast metadata repeated on every episode row). Choosing episodes automatically fetches the RSS feed even if includeEpisodes is off. Options: podcasts = One row per podcast; episodes = One row per episode.episodes
maxEpisodesNoMax episodes per podcast — Enter how many of the most recent episodes to read from each podcast's RSS feed, e.g. 20. Only used when includeEpisodes is on and outputMode is episodes.
searchLimitNoResults per search term — Enter how many podcasts each search: term should return, e.g. 25. Only affects rows starting with search: — an id, URL or feed entry always resolves to exactly one podcast.
includeEpisodesNoFetch episodes from RSS — Keep this on to fetch each podcast's own RSS feed (via its feedUrl) and read its language, full description and website — and, in episodes output mode, its episode list. Turning this off skips the RSS request entirely and leaves those fields null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses the notable behavioral facts: a per-episode billing cost against the user's Apify account, the fact that the show's own RSS feed is fetched for episode data, and that output is one row per podcast or episode. It omits auth requirements and rate-limit/error behavior, but the cost and data-source disclosures are unusually valuable.

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?

Two sentences, front-loaded with the input/output contract and closing with the cost model. Dense and largely waste-free, though the parenthetical pricing note is a slight digression from the operational instructions.

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 six-parameter scraper with no output schema and no annotations, it covers inputs, row-level output shape, the RSS dependency, and cost. Missing only auth/permission prerequisites and failure handling, which keeps it just short of fully complete.

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 the schema already documents all six parameters in detail. The description repeats the accepted input forms but adds no syntax or format detail beyond what the parameter descriptions provide, so baseline 3 is correct.

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?

States a specific verb and resource (Apple Podcasts lookup) and enumerates the four accepted input forms (id, URL, RSS feed, search term), plus what comes back (metadata and full episode list). No sibling tool covers podcasts, so the platform 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?

The enumerated input formats make clear when the tool applies, and the schema notes for country/searchLimit spell out which entries each option affects. It stops short of explicit when-not or alternative-tool routing, but siblings are all other platforms so there is little ambiguity to resolve.

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