Search PodLearn library AND PodcastIndex.org (4M+ podcasts) by keyword. Also resolves Spotify/Apple Podcasts URLs. Returns rows tagged with source: local|podcastindex|spotify. First move when the user names a podcast/host but you don't have its id.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search keywords or a podcast URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. Description adds behavioral details: searches multiple sources, resolves URLs, and returns tagged rows. No contradiction.
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 sentences, no fluff, and the most critical information (what it does and when to use) is front-loaded. Every sentence adds value.
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?
For a simple search tool with one parameter and no output schema, the description covers purpose, scope, behavior, and usage guidance comprehensively. No gaps given the tool's complexity.
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% with one parameter described as 'Search keywords or a podcast URL.' Description adds that it resolves Spotify/Apple Podcasts URLs and returns rows with source tags, augmenting the parameter's meaning 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?
Description clearly states it searches both PodLearn library and PodcastIndex by keyword, and resolves Spotify/Apple Podcasts URLs. It distinguishes from siblings like search_episodes and search_youtube by focusing on podcasts and being designated as the first move for identifying podcasts/hosts without IDs.
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 'First move when the user names a podcast/host but you don't have its id,' providing clear when-to-use guidance. Does not explicitly exclude other cases, but the context implies it's the starting point for podcast identification.
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.
Tools are largely distinct, covering separate actions (search, get, list, generate, transcribe, save). The main potential confusion is between list_episodes and list_feed_episodes, but descriptions clearly separate local from external.
All tools follow consistent verb_noun snake_case patterns (get_, list_, search_, generate_, transcribe_, save/remove), with no mixed conventions or unexpected styles.
25 tools is at the high end for a server of this scope. The broad domain justifies many functions, but the count feels heavy and some tools could be consolidated without losing clarity.
Discovery, ingestion, transcription, lesson generation, and user account management are all well covered. Minor gaps exist, such as no way to delete or update lessons beyond save/remove.