Skip to main content
Glama

Itunes Search Top Podcasts

itunes_search_top_podcasts
Read-onlyIdempotent

Apple Podcasts chart, read from Apple's RSS Marketing Tools feed, the top-ranked shows in one storefront country (default us), up to 100 entries. Each entry returns the show name, publisher, Apple id, genre list, release date, artwork URL and Apple Podcasts link. Answers which podcasts are most popular on Apple Podcasts right now in the US or another country.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 25,
      "country": "us"
    },
    "name": "itunes_search_top_podcasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
countryNo

Output Schema

NameRequiredDescriptionDefault
feedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety bar is low. The description nonetheless adds real context beyond them: the upstream data source, the default storefront (us), and a hard cap of 100 entries, which tells the agent the result set is bounded and non-mutating.

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?

Two sentences, front-loaded with the source and scope, and every clause carries information (source, scope, cap, returned fields, use case). The final sentence partially restates the first's scope rather than advancing it.

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?

An output schema exists, so the description needn't document return values, and it lists the entry fields only as a light orientation. With annotations covering the safety profile and both parameters addressed, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description has to carry the parameter burden, and it does: 'country (default us)' documents the default for one param and 'up to 100 entries' documents the effective ceiling for the other. It leaves the limit's own default and any country format (e.g. ISO code) unstated, which keeps it from a 5.

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 names a specific resource and scope: the Apple Podcasts chart read from Apple's RSS Marketing Tools feed, limited to one storefront country. The word 'chart'/'top-ranked' plus the per-entry field list makes clear this is a popularity ranking, not a free-text search like the itunes_search_search/lookup siblings.

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?

The closing sentence gives an implied use case ('Answers which podcasts are most popular on Apple Podcasts right now in the US or another country'), which is enough to infer when to reach for it. There is no explicit when-not guidance or named alternative for keyword/title lookups, so the agent must infer the boundary from the sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.