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 get normalized results from Apple's public iTunes Search API. Filter by country, language, and page to find episodes for research or discovery.

Instructions

Search Apple Podcasts episodes. Returns normalized Apple Podcasts episodes from Apple's public iTunes Search API.

Input Schema

TableJSON 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

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only mentions 'returns normalized Apple Podcasts episodes' without detailing traits like data freshness, rate limits, or limitations of the iTunes Search API. The term 'normalized' is vague and insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is succinct (one and a half sentences) but lacks structure. It front-loads the purpose but does not efficiently convey critical information like supported parameters or return behavior. Could be more informative without added length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters and no output schema, the description omits important context: what 'normalized' means, pagination behavior, or typical use cases. For a search tool with multiple sibling tools, this is incomplete and may lead to incorrect invocation.

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 all parameters have descriptions in the schema. The description adds no additional meaning beyond the schema, such as clarifying how 'country' or 'lang' affect results or how pagination works with 'limit' and 'page'. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Search Apple Podcasts episodes' with a verb and resource, clearly identifying the tool's function. However, it does not distinguish from sibling tools like apple_podcasts_search (which searches shows) or apple_podcasts_show_episodes, missing an opportunity to differentiate.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as apple_podcasts_search or apple_podcasts_show_episodes. The description does not include any context about prerequisites, appropriate search scenarios, or 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