Podcast Index MCP

List shows that take listener payments

list_value_podcasts

Read-onlyIdempotent

List podcast feeds that carry a value block, paging through the full value-for-value directory to find shows accepting direct listener payments or gauge the size of this segment.

Instructions

Every feed in the index carrying a value block, paged. This is the whole value-for-value corner of podcasting as a list, which is useful for sizing it or for finding shows that have opted into direct listener payment. Use start_at to page: the list is large.

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

Input Schema

Name	Required	Description
`max`	No	How many to return. Defaults to 100.
`start_at`	No	Feed id to resume from, for paging through the list.
`time_splits_only`	No	Only feeds using value time splits, which pay different recipients during different parts of an episode.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safe read-only, idempotent, non-destructive nature of the tool. The description adds useful behavior beyond that by disclosing that the list is paged and large, and by directing the agent to use start_at for paging.

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?

The description is two sentences with no filler. The first sentence states the resource and paging, and the second sentence explains why the tool matters and how to page, making every sentence purposeful.

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?

For a simple read-only list tool with fully documented optional parameters and strong annotations, the description provides enough scope, purpose, and pagination guidance to invoke it correctly. There is no output schema, so a bit more detail about the response shape would be nice, but it is not essential for correct selection and invocation.

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 description coverage is 100%, and each parameter already has a meaningful description in the schema. The tool description only reiterates the start_at paging behavior without adding new parameter semantics, so the schema carries the weight here.

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 opens with 'Every feed in the index carrying a value block, paged,' naming a specific verb and resource with a clear scope. It also positions the tool as the whole value-for-value list, distinguishing it from siblings like get_value_block or get_episode_value that target individual feeds or episodes.

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 description gives clear usage context: it is useful for sizing the value-for-value space or finding shows that accept listener payments. It also instructs paging with start_at because the list is large, but it does not explicitly name alternatives or state when not to use this tool.

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