Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apple_podcasts_search

Search Apple Podcasts shows by term to get normalized show data from iTunes Search API; filter by country, language, page, and limit.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResult language tag
pageNoSearch page number (1-based)
termYesSearch term
limitNoNumber of shows 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

B3.1/5.0
Behavior2/5

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

With no annotations, description carries full burden. Mentions data source but omits behavioral traits like rate limits, result ordering, default behavior for limit/page, or any destructive actions.

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?

Single sentence is concise and front-loaded with the main action. However, it could be slightly more informative without losing conciseness.

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?

For a tool with 5 parameters, no output schema, and sibling tools, the description is too sparse. Lacks explanation of pagination, country/lang semantics, and how results are formatted. Does not compensate for missing annotations.

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 baseline 3 applies. Description adds no additional meaning beyond what the schema already provides for parameters. No enrichment of parameter purpose or examples.

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?

Clearly states verb 'Search' and resource 'Apple Podcasts shows'. Distinguishes from sibling tools like apple_podcasts_charts or apple_podcasts_episodes_search by specifying shows. Also mentions normalized results and the data source.

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 on when to use this tool vs alternatives like apple_podcasts_charts for top charts or apple_podcasts_show for details. No context about prerequisites or exclusions provided.

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