Rephonic

Official

by getrephonic

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

search_episodes

Search podcast episodes by matching titles, show notes, and transcripts using queries and filters.

Instructions

Search for episodes. Matches against episode titles, show notes, and full transcripts. Specify either query or filters or both.

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_episodes"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number, starts at 1.
`query`	No	Search query. Supports parentheses, quotes, AND, OR and -negation.
`filters`	No	Advanced search filters, comma-separated.
`per_page`	No	Results per page, max 100. Default: 50.
`highlight`	No	If true, query matches in title, show notes and transcript are returned with HTML <b> tags.
`threshold`	No	Only return episodes published within the last N seconds. Max 1209600 (14 days).
`podcast_id`	No	Scope results to a single podcast by its Rephonic ID (e.g. 'the-daily').

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It discloses that it searches titles, show notes, and transcripts, but does not mention pagination behavior, rate limits, authentication needs, result ordering, or what happens if no query/filters are given. Some transparency, but gaps remain.

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?

The description is very concise: two sentences with no unnecessary words. The first sentence states the purpose, the second gives a usage hint. Every sentence is valuable.

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

Completeness2/5

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

Given the tool has 7 parameters, no output schema, and is a search endpoint, the description is incomplete. It does not explain return format (e.g., list of episodes, count), result ordering, or behavior when no match is found. The context of sibling tools suggests this is a search function, but missing details hinder completeness.

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 100%, so baseline is 3. The description adds meaning by stating that the tool matches against specific fields and that query and filters can be used independently or together. However, this does not significantly exceed what the schema already conveys.

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

Purpose5/5

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

The description clearly states the verb 'Search' and the resource 'episodes', and specifies that it matches against episode titles, show notes, and full transcripts. This distinguishes it from siblings like list_episodes and get_episode.

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

Usage Guidelines3/5

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

The description mentions that users can specify either query or filters or both, but does not provide guidance on when to use this tool versus alternative tools like list_episodes or get_episode. No exclusions or when-not-to-use instructions are given.

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