Transistor-MCP

list_shows

Retrieve all podcast shows from your Transistor.fm account with optional pagination, search, and privacy filters.

Instructions

List all shows in your Transistor.fm account

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_shows"
  }
}

Input Schema

Name	Required	Description
`per`	No	Items per page (default 10, max 100)
`page`	No	Page number for pagination
`query`	No	Search query to filter shows
`private`	No	Filter for private shows

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 25, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., that it is read-only, effects of pagination, rate limits). For a list tool, additional context about iteration or data volume would be beneficial.

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 sentence, which is concise but lacks structure. It could be improved by front-loading key details like pagination or search capability. Every sentence earns its place, but it is too minimal.

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 no output schema and limited annotations, the description is incomplete. It does not explain return structure, pagination behavior, or that parameters like 'query' and 'private' allow filtering. More context is needed for effective use.

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?

All 4 parameters have descriptions in the schema (100% coverage), so the description adds no new meaning. The baseline of 3 is appropriate; the description does not compensate or enhance parameter understanding.

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 'List all shows in your Transistor.fm account' uses a specific verb ('List') and resource ('shows'), clearly indicating the tool's function. It distinguishes from sibling tools like 'get_show' (single show) and 'list_episodes' (different resource).

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 guidance is provided on when to use this tool versus siblings, such as 'list_episodes' or 'get_show'. There is no mention of pagination, search, or filtering contexts, leaving the agent without direction.

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