Skip to main content
Glama
Red5d

Jupiter Broadcasting Podcast Data MCP Server

by Red5d

get_transcript

Retrieve podcast episode transcripts by providing show name and episode number. Access text content from Jupiter Broadcasting podcasts for analysis or reference.

Instructions

Get the transcript for a specific episode.

Args: show_name: Name of the show episode_number: Episode number

Returns: Dictionary containing the transcript text or error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
show_nameYes
episode_numberYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary MCP tool handler registered with @mcp.tool(). Delegates to rss_parser.get_transcript, handles errors, and formats the response as a dictionary.
    @mcp.tool()
    def get_transcript(show_name: str, episode_number: str) -> Dict[str, Any]:
        """Get the transcript for a specific episode.
        
        Args:
            show_name: Name of the show
            episode_number: Episode number
        
        Returns:
            Dictionary containing the transcript text or error message.
        """
        try:
            transcript = rss_parser.get_transcript(show_name, episode_number)
            if transcript:
                return {"transcript": transcript}
            else:
                return {"error": f"Transcript not available for episode '{episode_number}' in show '{show_name}'"}
        except Exception as e:
            return {"error": f"Failed to retrieve transcript: {str(e)}"}
  • Core implementation logic: retrieves the episode data, extracts the transcript URL, fetches and returns the transcript text.
    def get_transcript(self, show_name: str, episode_number: str) -> Optional[str]:
        """Get transcript for an episode."""
        episode = self.get_episode(show_name, episode_number)
        if not episode:
            return None
        
        transcript_url = episode.get("transcript_url")
        if not transcript_url:
            return None
        
        try:
            response = requests.get(transcript_url, timeout=30)
            response.raise_for_status()
            return response.text
        except Exception as e:
            print(f"Error fetching transcript: {e}")
            return None
  • Extracts podcast:transcript XML elements during episode parsing to populate transcript_url used by get_transcript.
    transcript_elems = item.findall('.//{https://podcastindex.org/namespace/1.0}transcript')
    for transcript in transcript_elems:
        transcript_url = transcript.get("url")
        transcript_type = transcript.get("type", "")
        if transcript_url:
            episode_data["transcript_urls"].append({
                "url": transcript_url,
                "type": transcript_type,
                "language": transcript.get("language", "en-us")
            })
    
    # For backward compatibility, set transcript_url to the first available transcript
    if episode_data["transcript_urls"]:
        episode_data["transcript_url"] = episode_data["transcript_urls"][0]["url"]
    else:
        episode_data["transcript_url"] = None
  • Explicit registration of the get_transcript tool using FastMCP decorator.
    @mcp.tool()
  • Supporting function to locate the specific episode by GUID or podcast:episode number, required by get_transcript.
    def get_episode(self, show_name: str, episode_number: str) -> Optional[Dict[str, Any]]:
        """Get specific episode data."""
        feed_root = self._get_feed(show_name)
        if feed_root is None:
            return None
        
        # Find all item elements (episodes)
        items = feed_root.xpath('//item')
        for item in items:
            # Check GUID
            guid_elem = item.find('guid')
            if guid_elem is not None and guid_elem.text == episode_number:
                return self._parse_episode(show_name, item)
            
            # Check podcast:episode number
            episode_elem = item.find('.//{https://podcastindex.org/namespace/1.0}episode')
            if episode_elem is not None and episode_elem.text == episode_number:
                return self._parse_episode(show_name, item)
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 of behavioral disclosure. It mentions that the tool returns a 'Dictionary containing the transcript text or error message,' which gives some insight into output behavior, but it does not cover critical aspects like authentication needs, rate limits, error conditions beyond generic messages, or whether it's a read-only operation. For a tool with zero annotation coverage, this is insufficient.

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 and front-loaded, with the purpose stated first, followed by structured sections for Args and Returns. Each sentence earns its place, but the Args section could be more integrated into the flow. Overall, it is efficient with minimal waste.

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's moderate complexity (2 required parameters) and the presence of an output schema (which handles return values), the description is somewhat complete. It covers the basic purpose and parameters, but gaps remain in usage guidelines and behavioral transparency. With no annotations and incomplete parameter details, it is adequate but has clear room for improvement.

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?

The schema description coverage is 0%, so the description must compensate. It lists the parameters (show_name, episode_number) and their roles, adding meaning beyond the bare schema. However, it does not provide details on format (e.g., episode_number as string vs. integer), constraints, or examples. With 2 parameters and some semantic clarification, it meets the baseline but lacks depth.

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: 'Get the transcript for a specific episode.' It specifies the verb ('Get') and resource ('transcript'), but does not explicitly differentiate from sibling tools like get_episode or search_episodes, which might also retrieve episode-related data. This makes it clear but not fully sibling-distinctive.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like get_episode or list_shows, nor does it specify contexts or exclusions for usage. This lack of comparative guidance leaves the agent without clear direction for tool selection.

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