List episodes - Lists episodes with parsed frontmatter (guest, title, duration, youtube_url, etc.) and their canonical resource URIs.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | ||
| limit | No | ||
| cursor | No | Opaque pagination cursor | |
| x-hapi-auth-state | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It reveals that results include parsed frontmatter and resource URIs, but it does not mention pagination behavior (despite the cursor parameter), authentication needs (x-hapi-auth-state), or default limits. These are significant gaps for an agent invoking the tool correctly.
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?
The description is a single sentence that is efficiently sized, but it contains minor redundancy ('List episodes' and 'Lists episodes'). It is generally front-loaded and easy to parse, though the repetition could be trimmed.
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 tool has pagination (cursor), sorting, limits, and auth-state parameters, plus sibling tools that could cause confusion, the description is too sparse. It does not explain pagination flow, default sort order, or when to use this list endpoint versus sibling guest-specific endpoints, leaving the agent under-informed for correct invocation.
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 description coverage is only 25% (only 'cursor' is described). The description does not compensate for the undocumented parameters (sort, limit, x-hapi-auth-state). It adds no meaning beyond what the schema already provides, so the agent is left without guidance on valid values or effects of these parameters.
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 the clear verb 'List' with the resource 'episodes' and adds specifics ('parsed frontmatter (guest, title, duration, youtube_url, etc.) and their canonical resource URIs'). This distinguishes it from sibling tools like getEpisodesGuest, which likely target individual guests.
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 general listing of episodes but does not explicitly state when to use this tool over siblings (e.g., getEpisodesGuest). No exclusions or alternative guidance is provided, so usage context is only implied by the name and generic list phrasing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tool purposes are mostly distinct, but there is overlap: getEpisodesGuestMetadatajson and getEpisodesGuestTranscriptformat (with json format) both return metadata, and getSearch/postSearch are functionally identical except for HTTP method. Descriptions help, but an agent could easily select the wrong tool.
Names mix run-together path-like camelCase (getEpisodesGuestChunksChunkIdtxt) with a different style for postSearch. The 'get' prefix is consistent but 'post' breaks the pattern, and the lack of separators makes names difficult to parse.
8 tools is within the expected range, but the granularity is high—episode retrieval is split across card, metadata, transcript, chunks, and chunk text tools, which could be consolidated without losing functionality.
The domain is a read-only podcast transcript service. It covers listing episodes, retrieving metadata, retrieving transcripts in multiple formats, and searching across metadata and transcript text. No essential operations are missing.