Skip to main content
Glama
Sign In
Panda Federation Tools

Panda Federation Tools

by pandadad0214
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Podcast Leads Finder: Podcast Host Emails & Guest Booking List

podcast_leads_finder
Read-only

Find podcasts to pitch by topic and country, returning active shows with host contacts, emails from RSS feeds, websites, socials, episode details, and a guest signal as Excel or CSV.

Instructions

Use this to find podcasts to pitch by topic. Input: keywords and country. Output: one row per active show with host, contact email published in its RSS feed, website, socials, episodes, last episode date and a has-guests signal, plus Excel and CSV.

Runs the Apify Actor pandadad0214/podcast-leads-finder (https://apify.com/pandadad0214/podcast-leads-finder) on your own Apify account. Price: $0.004 per podcast found. Runs that find nothing are not charged per result. Spending is capped per call by run_max_charge_usd.

Input Schema

NameRequiredDescriptionDefault
sortByNoSort by. Relevance = Apple's search order. Newest episode = most recently active first. Most episodes = biggest back catalogs first. Choices: relevance = Relevance; newestEpisode = Newest episode; mostEpisodes = Most episodes.relevance
countryNoApple Podcasts country. 2-letter store country to search, e.g. US, GB, CA, AU, IN. Default US.US
keywordsNoTopics / keywords. Podcast topics to search on Apple Podcasts, one per line, e.g. real estate investing, SaaS marketing, women in business. Each keyword returns up to about 600 shows before filters. Leave empty for a 20-podcast demo.
languageNoLanguage. Optional. Keep shows whose feed language starts with this code, e.g. en, es, de.
deepSearchNoDeep search. On by default: also searches show descriptions and keywords, not just titles, for up to 3x more shows per keyword.
maxResultsNoMaximum podcasts. You pay per returned podcast, so this also caps the cost. Whole number, 1 to 3,000; default 100.
minEpisodesNoMinimum episodes. Optional. Skip shows with fewer episodes (e.g. 20 to skip brand-new shows). Default 0.
onlyWithEmailNoOnly podcasts with a contact email. Keep only shows that publish a contact email in their RSS feed (itunes:owner, managingEditor or the show description).
run_max_itemsNoOptional. Most results to return from this call (default from PANDA_MAX_ITEMS, 50). Also limits how many results the Actor produces and charges for, unless you set its own max field.
activeWithinDaysNoActive within (days). Keep only shows that published an episode in the last N days. 0 = include inactive shows. Default 90.
run_timeout_secsNoOptional. Seconds to wait for results (default from PANDA_TIMEOUT_SECS, 120; max 300).
guestFriendlyOnlyNoOnly podcasts that feature guests. Keep only shows where at least 30% of the last 20 episodes look like interviews (guest names, 'with', 'feat.', or podcast:person guest tags).
run_max_charge_usdNoOptional. Hard spending cap for this call in USD (default from PANDA_MAX_CHARGE_USD, 0.50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, non-idempotent, non-destructive, so the safety profile is covered. The description adds real value beyond that: per-result pricing of $0.004, no charge for empty runs, a per-call spending cap, and the requirement that it runs on the caller's own Apify account with a named Actor. It does not disclose runtime behavior such as typical latency or failure modes, so a 3 rather than higher.

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 short paragraphs, front-loaded with purpose, then output shape, then execution and pricing. Every sentence carries distinct information, and the repeated Actor URL is the only minor redundancy.

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?

With 13 optional parameters and no output schema, the description compensates well by enumerating the returned fields (host, RSS email, website, socials, episodes, last episode date, has-guests signal) and the Excel/CSV formats. The remaining gap is that it does not clarify how the safety or cost profile changes if run_max_items and maxResults conflict.

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 all 13 parameters are already documented, which sets the baseline at 3. The description adds only marginal parameter meaning, tying cost to returned results and noting that run_max_charge_usd caps spend per call, but it does not explain the interaction between maxResults, run_max_items, and the charge cap.

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?

Opens with a specific verb and resource plus the intent: "find podcasts to pitch by topic," then immediately names the inputs (keywords, country) and the per-show output. No sibling tool in the list covers podcast discovery, so the purpose is unambiguous without cross-referencing anything.

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?

Usage context is clear: pitch prospecting by topic and country, with the note that an empty keywords list returns a 20-podcast demo, which tells the agent how to probe cheaply. It stops short of explicit when-not-to-use guidance or named alternatives, so it is clear context rather than full routing.

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