Skip to main content
Glama

Search podcasts

search_podcasts
Read-onlyIdempotent

Search podcast metadata and transcripts. Text-only hits include snippets; full transcripts require get_podcast with opt-in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_podcasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20, max 100
offsetNo
personNoA speaker/host name; either name order works
seriesNoSeries title, partial (e.g. 'Cluster Conversations')
keywordNoEvery word must occur in the title, abstract or transcript; quote a phrase to match it exactly
year_toNoLatest year
languageNoName or ISO code — 'French', 'fr', 'fra' all match
year_fromNoEarliest year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  3. Changed7 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Matches title, abstract — and the transcript"New value: +"Every word must occur in the title, abstract or transcript; quote a phrase to match it exactly"
    • addedInput schema / properties / keyword / maxLength
      Added value: +1000
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Name or ISO code — 'French', 'fr', 'fra' all match",
      +  "maxLength": 1000,
      +  "type": "string"
      +}
    • addedInput schema / properties / person / maxLength
      Added value: +1000
    • addedInput schema / properties / series / maxLength
      Added value: +1000
    • changedInput schema / properties / year_from / description
      Previous value: -"Earliest episode year"New value: +"Earliest year"
    • changedInput schema / properties / year_to / description
      Previous value: -"Latest episode year"New value: +"Latest year"
  4. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: results are snippet-level only and full transcript retrieval is a separate, opt-in step. It says nothing about result ordering or pagination behavior, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler; the core scope comes first and the escape hatch to get_podcast follows immediately. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-optional-parameter search tool with no output schema and rich annotations, the description covers what matters most: what is searched and what shape results take. It omits nothing critical, though a note on default result volume or ranking would make it fully self-sufficient alongside the high-coverage schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 88%, and the schema already documents each of the 8 optional filters including keyword phrase-quoting and language name/ISO handling. The description adds no parameter-level meaning beyond that, and none is required — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Search podcast metadata and transcripts') and clarifies the depth limit — hits are snippets, not full transcripts. It distinguishes itself from get_podcast, but does not differentiate from the generic 'search' sibling, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent elsewhere for a concrete need: full transcripts require get_podcast with opt-in, which is a real when-to-use-another-tool rule. It gives no guidance on query construction strategy or when a person/series-targeted search beats a keyword search, so it is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.