Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

podcast_get_episodes

Read-onlyIdempotent

Retrieve episodes for a specific podcast from Podcast Index by podcast ID, with optional max results and API credentials.

Instructions

Get episodes for a podcast from Podcast Index.

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": {
      "id": "<id>"
    },
    "name": "podcast_get_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
maxNo
api_keyNo
api_secretNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only the data source name; it says nothing about credential requirements (api_key/api_secret present in the schema), result limits via max, pagination, or rate limits.

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

Conciseness4/5

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

A single short sentence, front-loaded with no filler. It is efficient but borders on under-specification given the four undocumented parameters.

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?

For a four-parameter tool with zero schema coverage and no output schema, the description should explain the id/max/credential parameters and what is returned. As written it leaves the agent guessing on nearly all of them.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description carries the full burden and fails. It never clarifies whether "id" is a Podcast Index podcast id or a feed id (ambiguity sharpened by the sibling podcast_by_feed_url), nor what "max" or the api_key/api_secret parameters do.

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?

States a specific verb and resource ("Get episodes for a podcast") and names the upstream source (Podcast Index), which separates it from generic search tools. It does not explicitly distinguish itself from close siblings like podcast_search_episodes or podcast_by_feed_url, so it falls 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 Guidelines2/5

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

There is no guidance on when to use this versus podcast_search, podcast_search_episodes, podcast_by_feed_url, or podcast_recent_episodes. The agent must infer that this tool is keyed by a podcast id rather than a query or feed URL.

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