Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_apple_podcasts_shows_item

Retrieve an Apple Podcasts show by numeric ID from a dataset to get show and artist names, genres, episode count, feed URL, artwork, and Apple URL; missing IDs return 404.

Instructions

Get an Apple Podcasts show from dataset. Returns one Apple Podcasts show from the dataset by its numeric show id. The record has show and artist names, genres, country, episode count (track_count), release date, feed URL, artwork and Apple URL. An id not in the dataset returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesApple Podcasts numeric show id (e.g. 173001861)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it identifies a read operation, lists the returned fields, and explicitly says a missing id returns 404. It does not cover auth, rate limits, or malformed-id behavior, but it is solid for a simple dataset lookup.

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 purpose is front-loaded and the return fields and error behavior are stated clearly. There is minor redundancy between the first two sentences, both of which restate the basic get-by-id operation, but the description remains compact and readable.

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 one-parameter dataset item lookup with no output schema, the description is complete enough: it names the resource, the identifier format, the returned fields, and the 404 case. An agent can invoke it correctly without additional guidance.

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%, and the single id parameter is already documented in the schema. The description repeats that it is a numeric show id and adds 404 behavior for unknown ids, but does not add syntax or format detail beyond the schema baseline.

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 uses a specific verb and resource ('Get an Apple Podcasts show') and states it returns one record from the dataset by numeric show id. This clearly distinguishes it from sibling search/facets tools, which would work from queries rather than a known id.

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?

Usage is implied: call this when you already have a numeric Apple Podcasts show id and need the full record. However, the description does not explicitly name the search sibling as the alternative when the id is unknown, nor does it state any other when-to-use conditions.

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