Skip to main content
Glama
Sign In
podcast-recommendations

podcast-recommendations

by surendranb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List podcast genres

list_genres
Read-onlyIdempotent

List valid genre names for use with roulette and trending queries. Retrieve the complete set of accepted genres to ensure accurate podcast recommendations.

Instructions

The genre names accepted by roulette/trending

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds the relationship to roulette/trending, which is useful context, but does not add details about the return format, ordering, or any side effects. With annotations handling the core behavioral guarantees, a mid score is appropriate.

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 that is front-loaded and contains no filler. Every word contributes to the meaning.

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

Completeness4/5

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

Given the tool has no parameters, no output schema, and annotations cover its safe/read-only nature, the description adequately indicates what it returns (genre names) and its relationship to sibling tools. It could be slightly more explicit about the output format (e.g., a list of strings), but the current wording is sufficient for correct invocation.

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

Parameters4/5

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

There are zero parameters, so per the rubric the baseline is 4. No additional semantic explanation is needed since the tool takes no arguments.

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 lists genre names and specifies they are the ones accepted by roulette/trending, distinguishing it from sibling tools. The verb 'list' and resource 'genres' are specific and unambiguous.

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

Usage Guidelines4/5

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

The phrase 'accepted by roulette/trending' implies this tool is used when you need genre names for those specific tools. It provides clear context for when to call it, though it does not explicitly mention when not to use it or name alternatives beyond the implicit sibling relation.

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