Skip to main content
Glama
Sign In
Rephonic

Rephonic

Official
by getrephonic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

feedback

Retrieve overall rating, review count, and AI-summarized insights from listener reviews for any podcast.

Instructions

Returns overall rating, total ratings/reviews count across various apps, and AI-generated summary insights of listener reviews.

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": "feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
podcast_idYesThe Rephonic podcast ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only states what is returned, not whether the tool is read-only, requires authentication, or has any side effects. The read-only nature is implied but not explicit.

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?

A single sentence of 17 words efficiently conveys the core purpose with no redundancy or filler. It is front-loaded with the verb and key results.

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 simplicity (one parameter, no output schema), the description is adequate but not thorough. It omits details about the format of the rating, apps covered, or how the AI summary is derived. A minimal but acceptable description for a straightforward data retrieval 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?

Schema coverage is 100%, so the baseline is 3. The description adds no parameter-specific context beyond the schema, which already explains 'podcast_id' as 'The Rephonic podcast ID.' No additional constraints or format details are provided.

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 tool returns overall rating, total counts across various apps, and AI-generated summary insights. It uses a specific verb 'Returns' and identifies the resource (feedback for a podcast), and distinguishes from the sibling 'reviews' tool by mentioning the AI summary.

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?

No explicit guidance on when to use this tool versus alternatives like 'reviews'. The description does not mention prerequisites, context, or when not to use. Usage is only implied by the description of what it returns.

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