Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

podcast_recent_episodes

Read-onlyIdempotent

Fetch recent podcast episodes from Podcast Index to support episode discovery and monitoring workflows.

Instructions

Get recent podcast episodes from Podcast Index.

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

Input Schema

NameRequiredDescriptionDefault
maxNo
api_keyNo
api_secretNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only the source name and the word 'recent'; it does not mention authentication requirements despite api_key/api_secret parameters, nor does it describe rate limits, pagination, or what 'recent' means in practice.

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

Conciseness3/5

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

The description is a single front-loaded sentence with no wasted words, but it is under-specified rather than optimally concise. It earns its place but could carry more useful detail without bloat.

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 three undocumented parameters, no output schema, and an open-world read operation, the description is too sparse. It does not explain authentication, the meaning of 'recent' (time window or count), or the return shape, leaving key context to inference.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate for three undocumented parameters. It says nothing about max, api_key, or api_secret, leaving the agent with no semantic guidance for any input.

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?

The description states a clear verb and resource ('Get recent podcast episodes') and names the data source ('Podcast Index'). It does not distinguish the tool from siblings like podcast_trending or podcast_get_episodes, leaving ambiguity about what 'recent' means relative to those alternatives.

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 tool versus podcast_get_episodes, podcast_search_episodes, or podcast_trending. The agent must infer selection criteria from the name alone, with no explicit conditions or exclusions.

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