Podcast Index MCP

Get one episode's payment split

get_episode_value

Read-onlyIdempotent

Retrieve the value block for a single episode using podcast and episode GUIDs to see the payout split and who received a share.

Instructions

The value block for a single episode, which can differ from the show's. Publishers override the split per episode to pay a guest a share, so this is how you see who was cut in on a particular conversation. Needs both the podcast GUID and the episode GUID, because that is the only pair this endpoint accepts.

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": {
      "podcast_guid": "<podcast_guid>",
      "episode_guid": "<episode_guid>"
    },
    "name": "get_episode_value"
  }
}

Input Schema

Name	Required	Description	Default
`episode_guid`	Yes	The episode's GUID from the RSS feed, from get_episodes.
`podcast_guid`	Yes	The show's podcast GUID, from get_podcast.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive. The description adds meaningful behavioral context not in annotations: why the split may differ from the show's, the override mechanism, and that the endpoint only accepts the exact pair of GUIDs. No contradictions.

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?

Three sentences, each earning its place: first defines the resource, second explains why it exists, third states the requirement. Slightly awkward phrasing in the first sentence ('The value block for...') but no wasteful content.

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 tool with two well-documented parameters and no output schema, the description provides enough context to understand what data is returned and why both IDs are necessary. It does not detail the return format, but annotations and the title compensate adequately.

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?

Schema coverage is 100%, so both parameters are already documented with source hints. The description adds value by emphasizing that both GUIDs are required together and that this pair is the only accepted combination, which clarifies the relationship between parameters beyond the schema.

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 identifies a specific resource: the payment split/value block for a single episode. It explains the purpose ('see who was cut in on a particular conversation') and explicitly distinguishes this from the show-level value block ('can differ from the show's'), which differentiates it from sibling get_value_block.

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 concrete context for when to use it: when a publisher overrides the split per episode and you need to see who was paid on a particular episode. It also states the prerequisite of needing both GUIDs, but does not explicitly name an alternative tool or say when not to use it.

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