Skip to main content
Glama
Sign In
Rephonic

Rephonic

Official
by getrephonic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

episode_transcript

Retrieve the full transcript for a podcast episode using its Rephonic ID. Not available for all episodes.

Instructions

Get the full transcript for an individual episode. Not available for all episodes. May include speaker name mapping.

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": {
      "episode_id": "<episode_id>"
    },
    "name": "episode_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
episode_idYesThe Rephonic episode ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It notes 'May include speaker name mapping' but omits details like response format, rate limits, or authentication needs. Insufficient for a mutation-like retrieval.

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 no wasted words. Information is front-loaded and efficient.

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?

No output schema and no description of return format (e.g., plain text, JSON). Does not mention whether transcript is complete or truncated, nor any size limits. Incomplete for a content-returning tool.

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?

Only one parameter (episode_id) with 100% schema coverage. Description adds no meaning beyond the schema. Baseline score of 3 is appropriate.

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?

Description clearly states the action ('Get') and resource ('full transcript') with scope ('individual episode'). It distinguishes from siblings like get_episode or list_episodes, but could be slightly more precise.

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

Usage Guidelines2/5

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

Only mentions a limitation ('Not available for all episodes') but does not guide when to use this tool versus alternatives like get_episode or search_episodes. No explicit context for usage.

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

Deploy Server

Other Tools