Fetch Apple Podcasts show metadata by ID. Returns normalized details like title, author, and episode info from Apple's iTunes Lookup API, with optional language and country settings.
Retrieve Apple Podcasts show details. Returns normalized show metadata from Apple's public iTunes Lookup API.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Apple Podcasts show ID | |
| lang | No | Result language tag | |
| country | No | Two-letter storefront country code |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility for behavioral disclosure. It only mentions the source API and normalized metadata, lacking details on rate limits, authorization, error handling, or whether the lookup is read-only. Significant gaps exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise with two sentences, front-loading the purpose. It is efficient but could include more context without harming conciseness, such as noting the output format.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given three parameters and no output schema, the description provides the basic purpose and API source. However, it does not explain what 'normalized show metadata' includes, nor does it cover parameter interactions or limitations. Adequate but leaves gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers 100% of parameters with descriptions, so the description does not need to add much. However, it adds no additional meaning beyond what the schema already provides, such as parameter constraints or formatting hints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves Apple Podcasts show details using the iTunes Lookup API. The verb 'retrieve' and resource 'show details' make the purpose specific, and it distinguishes from sibling tools like apple_podcasts_search and 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for obtaining show details by ID, but provides no explicit guidance on when to use this tool versus alternatives such as apple_podcasts_search or apple_podcasts_show_episodes. No exclusions or conditions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.