Rephonic

Official

by getrephonic

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

list_episodes

Returns every episode of a podcast in chronological order, with optional search filters by query.

Instructions

Returns every episode for a given podcast in chronological order, including YouTube videos if found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "podcast_id": "<podcast_id>"
    },
    "name": "list_episodes"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number, starts at 1.
`query`	No	Filter episodes by search query. Matches titles, show notes, and transcripts.
`per_page`	No	Results per page, max 25. Default: 25.
`podcast_id`	Yes	The Rephonic podcast ID (e.g. 'the-daily').

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided, so the description must convey behavior. It mentions chronological order and YouTube inclusion, but fails to disclose pagination, authentication needs, or response format.

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?

Single, front-loaded sentence with no wasted words. Every part adds value.

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

Completeness3/5

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

Given the tool's simplicity and full schema coverage, the description is adequate but could mention output structure or common use cases. No output schema, but description doesn't compensate.

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 coverage is 100% with descriptions for all parameters. The description adds no additional parameter meaning beyond the schema, so baseline 3 is appropriate.

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 'returns', the resource 'episodes', and the scope: 'for a given podcast in chronological order, including YouTube videos if found.' It distinguishes from siblings like search_episodes (cross-podcast) and get_episode (single 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?

No explicit guidance on when to use this tool versus alternatives like search_episodes. The purpose is implied but not contrasted with siblings.

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