podcasts
Server Details
An MCP server that provides tools to discover and retrieve podcast episodes transcripts.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 5 of 5 tools scored. Lowest: 3.6/5.
Each tool serves a distinct purpose: two different search methods (keyword vs. semantic), one for listing episodes, one for transcripts, and one for feedback. No ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.
5 tools is on the lower end but appropriate for focused podcast episode retrieval and searching. Each tool has a clear role.
Covers core operations: listing, searching (two types), and transcript retrieval. Missing episode metadata details (title, date, description) which agents might need for user-facing tasks.
Available Tools
5 toolsget_latest_episodesGet Latest EpisodesARead-onlyIdempotentInspect
Return the most recent transcript-ready episodes across the full podcast catalog.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort order for results. `relevance` ranks full-text searches first and falls back to newest-first when no query is provided. | published_desc |
| limit | No | Maximum number of episodes to return. Must be between 1 and 50. | |
| cursor | No | Zero-based episode offset for pagination. Use the `next_cursor` returned by a prior search/listing call to fetch the next page of results. | |
| published_after | No | Inclusive lower publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. | |
| published_before | No | Inclusive upper publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. |
Output Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | Number of episodes returned on this page. |
| episodes | Yes | Matching transcript-ready episodes. |
| next_cursor | No | Cursor to pass to the next search call to retrieve the next page of results, or null if there are no more pages. |
| total_count | Yes | Total number of matching transcript-ready episodes across all pages. |
| total_count_is_approximate | No | When true, `total_count` is a lower bound — more matches may exist than were counted. False for exact lexical/date counts; can be true only for semantic results (e.g. the topic-search fallback). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It adds the useful context that episodes are 'transcript-ready', but does not disclose pagination or other behavioral details. With good annotations, this is adequate.
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?
A single sentence that is front-loaded with the core action and scope. No wasted words; every part earns its place.
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?
The description is minimal but sufficient given the presence of a full output schema (not shown) and detailed parameter descriptions. It could mention pagination but the schema covers it. The 'transcript-ready' constraint is a key detail.
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?
Schema coverage is 100% and each parameter has a detailed description. The tool description adds no parameter-level information beyond what the schema provides, which is acceptable given the schema richness.
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 uses a specific verb ('Return') and resource ('episodes'), and adds qualifiers ('most recent', 'transcript-ready', 'full catalog'). It clearly states what the tool does, but does not explicitly distinguish itself from sibling tools like search_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 that this tool is for browsing the latest episodes across the entire catalog, but it does not provide explicit guidance on when to use this tool versus the search alternatives. No exclusions or alternatives are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_transcriptGet TranscriptARead-onlyIdempotentInspect
Fetch a bounded transcript chunk for a specific episode using its show and episode GUIDs. Use next_cursor to continue reading.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Zero-based character offset into the transcript. Use the `next_cursor` returned by a prior get_transcript call to fetch the next chunk. | |
| max_chars | No | Target maximum number of transcript characters to return. Chunks prefer natural boundaries and may be slightly shorter. Must be between 100 and 20000. | |
| show_guid | Yes | Podcast show GUID returned by `search_episodes` or `get_latest_episodes`. | |
| episode_guid | Yes | Episode GUID returned by `search_episodes` or `get_latest_episodes`. |
Output Schema
| Name | Required | Description |
|---|---|---|
| text | Yes | Transcript chunk text. |
| char_end | Yes | Exclusive zero-based end offset of this chunk in the complete transcript. |
| has_more | Yes | Whether another get_transcript call is needed to continue reading. |
| show_guid | Yes | Podcast show GUID requested by the client. |
| char_start | Yes | Inclusive zero-based start offset of this chunk in the complete transcript. |
| show_title | Yes | Podcast show title. |
| next_cursor | No | Cursor to pass to the next get_transcript call, or null at the end. |
| total_chars | Yes | Total character count of the complete transcript text. |
| episode_guid | Yes | Podcast episode GUID requested by the client. |
| rss_feed_url | Yes | RSS feed URL for the podcast show. |
| episode_title | Yes | Podcast episode title. |
| published_date | Yes | Episode publication timestamp in ISO 8601 format. |
| duration_seconds | No | Episode duration in seconds when available from the source feed. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare safe read-only behavior (readOnlyHint, idempotentHint). Description adds valuable context about chunk boundaries and cursor-based pagination, enhancing transparency.
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?
Two concise sentences with no redundant words. Front-loaded with key action and resource.
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 high schema coverage, output schema present, and clear annotations, the description covers all essential behavioral aspects (chunking, cursor usage) for an agent to use the tool correctly.
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?
Schema coverage is 100% and each parameter is well-described. Description adds minor detail (zero-based offset, natural boundaries) but mostly repeats what schema provides, so baseline 3 is appropriate.
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?
Description clearly states verb (Fetch), resource (transcript chunk), and scope (specific episode via GUIDs). It distinguishes from sibling tools like search_episodes which search for episodes, not transcripts.
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?
Explicitly says to use `next_cursor` for continuation, implying pagination. No explicit when-not-to-use or alternatives, but context makes it clear this tool is for transcript retrieval only.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
give_feedbackGive FeedbackAInspect
Send structured feedback about bugs, missing data, unclear behavior, or feature requests.
| Name | Required | Description | Default |
|---|---|---|---|
| feedback | Yes | Feedback for the server team. Include the problem, missing capability, or suggested improvement without sensitive user data. |
Output Schema
| Name | Required | Description |
|---|---|---|
| status | Yes | Feedback persistence status. |
| message | Yes | Human-readable result summary. |
| feedback_id | Yes | Stable feedback identifier. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint=false, destructiveHint=false) are consistent. Description adds behavioral note about avoiding sensitive data. No contradictions.
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?
Single sentence, no fluff, front-loaded with verb and resource. Every word serves a purpose.
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 simplicity, description covers purpose and constraint. Output schema exists but not used in description. Could mention result but not necessary.
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?
Schema covers the single parameter with description; tool description adds minor context (types of feedback) but doesn't significantly increase understanding beyond schema.
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?
Clear verb 'send' plus resource 'structured feedback' with explicit types: bugs, missing data, unclear behavior, feature requests. Distinguishes from sibling tools about episodes/transcripts.
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?
Implied usage for reporting issues, but no explicit guidance on when to use vs alternatives, nor when not to use. Lacks exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_episodesSearch EpisodesARead-onlyIdempotentInspect
Search indexed podcast episodes by keyword or show name and return the show/episode GUIDs needed for transcript retrieval.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort order for results. `relevance` ranks full-text searches first and falls back to newest-first when no query is provided. | relevance |
| limit | No | Maximum number of episodes to return. Must be between 1 and 50. | |
| query | No | Optional search keywords matched against indexed episode content. Use people, topics, companies, or phrases. | |
| cursor | No | Zero-based episode offset for pagination. Use the `next_cursor` returned by a prior search/listing call to fetch the next page of results. | |
| podcast_name | No | Optional podcast title or internal label to narrow results to a specific show. | |
| published_after | No | Inclusive lower publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. | |
| published_before | No | Inclusive upper publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. | |
| published_within_hours | No | Filter episodes published in the past X hours. Maximum 168 hours (1 week). |
Output Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | Number of episodes returned on this page. |
| episodes | Yes | Matching transcript-ready episodes. |
| next_cursor | No | Cursor to pass to the next search call to retrieve the next page of results, or null if there are no more pages. |
| total_count | Yes | Total number of matching transcript-ready episodes across all pages. |
| total_count_is_approximate | No | When true, `total_count` is a lower bound — more matches may exist than were counted. False for exact lexical/date counts; can be true only for semantic results (e.g. the topic-search fallback). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that it returns GUIDs for transcript retrieval, which is useful context but does not elaborate on pagination or other behaviors beyond what the input schema covers.
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?
Single sentence that front-loads the action and purpose. No redundant words; every part contributes meaning.
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 the presence of an output schema, 100% parameter schema coverage, and no required parameters, the description is adequate for a search tool. It could mention result structure briefly, but the output schema fills that gap.
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?
Schema coverage is 100%, so the schema already documents all 8 parameters thoroughly. The description mentions 'keyword or show name' which maps to 'query' and 'podcast_name', but adds no additional semantic value beyond the schema.
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 states a specific verb ('Search'), resource ('indexed podcast episodes'), and scope ('by keyword or show name'), and explicitly mentions the output ('show/episode GUIDs needed for transcript retrieval'). This clearly distinguishes from siblings like 'get_latest_episodes' or 'search_episodes_by_topic'.
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 context (keyword or show name search) but does not explicitly contrast with siblings like 'search_episodes_by_topic' or 'get_latest_episodes'. No when-not or alternative guidance is provided, though the purpose is clear enough to infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_episodes_by_topicSearch Episodes by TopicARead-onlyIdempotentInspect
Semantic topic search across the podcast catalog. Unlike search_episodes (which does lexical/keyword matching), this tool understands meaning: a query for 'AI safety' will match episodes about 'AI alignment', 'AGI risk', or 'frontier model evaluation' even if they don't contain the exact phrase. Returns ranked episodes with the matched topic phrases so you can explain why each result is relevant before fetching the transcript. Best for conceptual or thematic queries — use search_episodes instead when the user is looking for a specific person, product, or verbatim phrase.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of episodes to return. Must be between 1 and 50. | |
| topic | Yes | Semantic topic to find episodes about. Free-form phrasing welcome — the server embeds this string and finds episodes whose extracted topic phrases are closest in meaning. Good examples: 'AI safety', 'EU AI Act regulation', 'GPU supply constraints', 'Theo Epstein on roster construction'. Distinct from `search_episodes`, which performs lexical keyword matching. | |
| cursor | No | Zero-based episode offset for pagination. Use the `next_cursor` returned by a prior search/listing call to fetch the next page of results. | |
| show_guid | No | Optional canonical show GUID (as returned by `search_episodes` or `get_latest_episodes` in the `show_guid` field) to restrict topic search to a single podcast. Leave empty to search across all shows. | |
| published_after | No | Inclusive lower publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. | |
| published_before | No | Inclusive upper publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime. |
Output Schema
| Name | Required | Description |
|---|---|---|
| count | Yes | Number of episodes returned on this page. |
| query | Yes | The topic query that was embedded and searched. |
| episodes | Yes | Episodes ranked by best topic-phrase similarity to the query. |
| next_cursor | No | Cursor to pass to the next search call to retrieve the next page of results, or null if there are no more pages. |
| total_count | Yes | Number of matching episodes, counted over the nearest-match candidate window rather than the whole catalog. When `total_count_is_approximate` is true, treat this as a lower bound — broad queries may have more matches than reported. |
| total_count_is_approximate | No | True when the candidate window was exhausted, so `total_count` undercounts the true number of matches. When false, `total_count` is exact. Refine the query for tighter results if this is true and you need a complete set. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description explains the semantic mechanism (embedding and similarity matching), returns ranked episodes with topic phrases, and mentions explainability. Annotations (readOnlyHint, idempotentHint) are consistent with this read-only, idempotent behavior.
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?
Five sentences, all essential: purpose, contrast, behavior, usage guidance. Front-loaded with key distinction. No redundancy or fluff.
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 6 parameters, 1 required, and an output schema, the description covers input semantics, output format (ranked episodes with topic phrases), pagination via cursor, and filtering options. No gaps for a semantic search tool.
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?
Every parameter has a schema description, and the description adds context: examples for `topic`, source for `show_guid`, format for published_after. Schema coverage is 100%, and the description further enriches understanding.
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 'Semantic topic search across the podcast catalog' and contrasts with sibling `search_episodes` (lexical vs semantic), providing examples. It identifies the specific verb-resource combination and distinguishes from alternatives.
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?
Explicit guidance: 'Best for conceptual or thematic queries — use `search_episodes` instead when the user is looking for a specific person, product, or verbatim phrase.' Names the alternative and specifies when to use each.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!