Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apple_podcasts_episodes_search

Search Apple Podcasts episodes by keyword and refine by country, language, page, or limit to retrieve episode titles, shows, dates, and URLs.

Instructions

Search Apple Podcasts episodes. Searches Apple Podcasts episodes by term, which is required. country, lang, limit and page (1-based) refine the search. Each episode has its title, show_name, show_id, description, duration_millis, release_date, episode_url, preview_url, feed_url, genres and artwork.

Input Schema

NameRequiredDescriptionDefault
langNoResult language tag
pageNoSearch page number (1-based)
termYesSearch term
limitNoNumber of episodes per page
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully describes pagination as 1-based and lists the returned episode fields, but it does not mention ordering, rate limits, or other operational constraints. For a simple read-only search this is adequate but not rich.

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?

The description is front-loaded and appropriately sized. There is slight redundancy between the first two sentences, but overall every sentence contributes useful information, including the returned fields.

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 search tool with no output schema and no annotations, the description covers the core behavior, required parameter, refining parameters, pagination, and returned episode fields. An agent has enough information to call it 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 coverage is 100%, so the schema already documents all five parameters. The description adds a little meaning by saying `term` is required and that the other parameters refine the search, but it largely repeats what the schema provides.

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 gives a specific verb and resource: 'Search Apple Podcasts episodes.' It also clarifies that this searches episodes by a required term, which distinguishes it from show-specific episode listing tools such as apple_podcasts_show_episodes.

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

Usage Guidelines3/5

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

It states that `term` is required and that `country`, `lang`, `limit`, and `page` refine the search, so usage is implied clearly. However, it does not explicitly name alternatives or say when to use this instead of sibling tools like apple_podcasts_search or apple_podcasts_show_episodes.

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