Skip to main content
Glama
Red5d

Jupiter Broadcasting Podcast Data MCP Server

by Red5d

list_shows

Retrieve all available podcast shows from Jupiter Broadcasting for searching and episode access.

Instructions

List all available podcast shows.

Returns: List of show names available for searching and episode retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary handler for the 'list_shows' MCP tool. Decorated with @mcp.tool() for registration and execution. Delegates to rss_parser.get_shows() to retrieve the list of podcast shows.
    @mcp.tool()
    def list_shows() -> List[str]:
        """List all available podcast shows.
        
        Returns:
            List of show names available for searching and episode retrieval.
        """
        return rss_parser.get_shows()
  • Supporting method in PodcastRSSParser class that returns the keys (show names) from the configured feeds dictionary, used by the list_shows tool handler.
    def get_shows(self) -> List[str]:
        """Get list of available show names."""
        return list(self.feeds.keys())
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the return is a 'List of show names' and hints at usage for 'searching and episode retrieval,' but doesn't disclose behavioral traits like whether it's paginated, rate-limited, or requires authentication. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 description is appropriately sized with two sentences: one states the purpose, and the other explains the return value and usage. It's front-loaded with the main action, and every sentence adds value without waste. However, it could be slightly more structured by separating usage guidance more clearly.

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

Completeness3/5

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

Given the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is adequate but incomplete. It explains the purpose and return usage, but with no annotations, it should do more to cover behavioral aspects like performance or constraints. The output schema reduces the need to explain return values, but overall completeness is minimal viable.

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?

The tool has 0 parameters, and schema description coverage is 100%, so the baseline is high. The description adds value by clarifying the output's purpose ('available for searching and episode retrieval'), which goes beyond the empty schema. This compensates well for the lack of parameters, but doesn't reach a 5 as it could detail output format more.

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 clearly states the tool's purpose: 'List all available podcast shows' specifies the verb (list) and resource (podcast shows). It distinguishes from siblings like get_episode or get_transcript by focusing on shows rather than episodes or transcripts. However, it doesn't explicitly differentiate from search_episodes, which might also involve shows, keeping it from a perfect score.

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 description implies usage by stating 'available for searching and episode retrieval,' suggesting this tool is for initial discovery before using other tools. However, it lacks explicit guidance on when to use this vs. alternatives like search_episodes, and no exclusions or prerequisites are mentioned, making it only adequate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Red5d/jupiterbroadcasting_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server