ListenHub MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LISTENHUB_API_KEY | Yes | Your API key obtained from the ListenHub API Keys Settings page |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_speakersA | Get list of available published speakers for podcast generation. Supports filtering by language code (e.g. "zh", "en"). Returns speaker ID, name, language, gender and demo audio URL. Defaults to Chinese speakers if no language specified. |
| create_podcastA | Create a podcast episode with full generation (text + audio). Supports single-speaker (solo) or dual-speaker (dialogue) formats with 1-2 speakers (can use speaker names or IDs). Choose from 3 generation modes: quick (3-5 min podcast), deep (8-15 min podcast), or debate (5-10 min podcast). Accepts text or URL sources. This tool will automatically poll until generation is complete (may take several minutes). |
| get_podcast_statusA | Query detailed information of a podcast episode, including generation status, audio URLs, scripts, outline, and metadata. Does not poll - returns current status immediately. |
| create_podcast_text_onlyA | Create podcast episode with text content only (no audio generation). Supports single-speaker (solo) or dual-speaker (dialogue) formats with 1-2 speakers (can use speaker names or IDs). Choose from 3 generation modes: quick (3-5 min podcast), deep (8-15 min podcast), or debate (5-10 min podcast). This is the first stage of two-stage generation. After text generation completes, you can review the scripts. To use modified scripts, call generate_podcast_audio with customScripts parameter to override the generated scripts when generating audio. |
| generate_podcast_audioA | Generate audio for a podcast episode that already has text content. This is the second stage of two-stage generation. The episode must have contentStatus=text-success. You can optionally provide customScripts parameter to override the generated scripts when generating audio. NOTE: This is the ONLY way to use modified scripts - there is no separate tool to edit scripts after generation. |
| create_flowspeechA | Create a FlowSpeech episode by converting text or URL content to speech. Supports smart mode (AI-enhanced, fixes grammar) and direct mode (no modifications). This tool will automatically poll until generation is complete. |
| get_flowspeech_statusA | Query detailed information of a FlowSpeech episode, including generation status, audio URLs, scripts, outline, and metadata. Does not poll - returns current status immediately. |
| get_user_subscriptionA | Get current user subscription information, including subscription status, credit usage, plan details, and renewal status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_podcast_guide | Step-by-step guide for creating podcasts with speaker name resolution |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes, but there is some overlap between create_podcast and create_podcast_text_only + generate_podcast_audio, as they both handle podcast creation with different workflows. The descriptions clarify the differences, but an agent might initially be confused about which to use for text-only vs. full generation.
All tool names follow a consistent verb_noun pattern with snake_case, such as create_flowspeech, get_podcast_status, and get_speakers. This predictability makes it easy for agents to understand and navigate the tool set without confusion.
With 8 tools, the server is well-scoped for its podcast and speech generation domain. The tools cover creation, status checking, resource management, and user information, providing a balanced set without being overwhelming or insufficient for the intended workflows.
The tool set offers strong coverage for podcast and FlowSpeech generation, including creation, status retrieval, and speaker management. However, there is a notable gap in editing capabilities, as noted that there is no separate tool to edit scripts after generation, which could limit agent flexibility in iterative workflows.