Search episodes and transcripts (POST body) - Same search as GET /search, but parameters are provided in the request body. This is useful for longer filter payloads.
| Name | Required | Description | Default |
|---|---|---|---|
| undefinedBody | Yes | ||
| x-hapi-auth-state | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It adds behavioral context by specifying the POST body format and equating behavior to GET search. However, it omits details like authentication (x-hapi-auth-state appears in schema), return format, or pagination behavior, leaving notable gaps.
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, dense sentence that efficiently conveys the action, the distinction from GET, and the use case. Every phrase adds value with no redundancy.
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 tool has a complex nested schema with 10 fields and no output schema, yet the description provides only a high-level purpose and the POST/GET difference. It fails to explain key parameters (q, mode, limit, cursor) or return behavior, making it incomplete for correct invocation without additional documentation.
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 0% and the description does not explain any parameters. The phrase 'Same search as GET /search' implies shared semantics with the GET tool, but this description itself adds no meaning to the many nested fields (q, mode, guest, etc.), forcing the agent to rely on external knowledge of getSearch.
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 'Search episodes and transcripts' with a specific verb and resource. It also distinguishes itself from the GET /search sibling by noting it's the POST body variant, which makes its purpose unambiguous.
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?
It explicitly contrasts with GET /search ('Same search as GET /search') and provides a concrete usage criterion: 'useful for longer filter payloads.' This tells the agent when to choose this tool over the GET alternative.
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.