Skip to main content
Glama
Podcast MCP
by calebn

feed_read

Read an episode's podcast listing to inspect facts, provenance, missing values, show notes, XML, and show details before making edits.

Instructions

Read the episode's podcast listing: every fact with where it came from, and what is missing.

facts (default) is JSON: each value says whether it is derived, inherited, measured, minted, pinned (by a person, an agent or a guest, and whether the automatic value moved since) or pending with the edit that would fix it, plus findings tagged blocker, warn or info. notes_html is the show notes, item_xml the bare <item>, feed_xml the feed file and show which show the episode belongs to. Use this before feed_set. Not list_chapters_tool: chapters are edited there, never in the listing.

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

Input Schema

NameRequiredDescriptionDefault
viewNofacts
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose real behavior: the default JSON view reports per-value provenance (derived, inherited, measured, minted, pinned, pending) and findings tagged blocker/warn/info, including whether automatic values moved after a human/agent/guest pin. It does not mention permissions or any side effects, but for a read-style listing tool the disclosure is substantial.

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?

The opening sentence states scope, the default view and its payload come next, then the remaining views are enumerated compactly, and the routing rules close the text. It is dense but front-loaded and every clause carries information; the provenance vocabulary is verbose but necessary for interpreting the output.

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?

An output schema exists, so return values need not be re-explained, yet the description still characterizes each view's payload, which is more than required for a two-parameter read tool. The only real gap is the undocumented `project_path` parameter; nothing about how to call the tool correctly is missing otherwise.

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 description coverage is 0%, so the description must compensate, and it does for the important parameter by explaining what each `view` enum value returns: `notes_html` is the show notes, `item_xml` the bare `<item>`, `feed_xml` the feed file, `show` the owning show, and `facts` (default) the JSON provenance listing. The second parameter, `project_path`, is never mentioned, which keeps it short of a 5.

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 a specific verb and resource: 'Read the episode's podcast listing: every fact with where it came from, and what is missing.' It also names what it is not ('Not list_chapters_tool: chapters are edited there, never in the listing'), so an agent can distinguish it from both feed_set and list_chapters_tool.

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

Usage Guidelines5/5

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

It gives explicit ordering guidance ('Use this before feed_set') and an explicit exclusion with a reason ('Not list_chapters_tool: chapters are edited there, never in the listing'). Both when-to-use and when-not-to-use are stated rather than left to inference.

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