Skip to main content
Glama
Podcast MCP
by calebn

feed_set

Pin podcast episode listing fields such as intro, title, notes, season, or enclosure URL, and update shared show fields or link episodes to shows; blank text unsets a field.

Instructions

Pin one podcast-listing value, as an agent. An episode value undoes with history.

item.* keys are pinned on this episode. channel.* keys and show (link this episode to a show by name, creating it when new) change the show every episode shares, are saved in the show's file and are not undone by history.

field is a key from feed_read, such as item.intro, item.title, item.notes, item.enclosure.url, item.season or item.person[Name].href. Write the episode intro with item.intro: one or two sentences, plain text. Setting item.notes pins the whole notes text, so prefer item.intro. Blank text unsets. value is text; a number or true/false is read as its text, so 2 and "2" both set season 2. Chapters, clips, speakers and transcripts are edited where they live, not here. Returns the updated facts. Not add_chapter_tool.

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": {
      "field": "<field>",
      "value": "<value>"
    },
    "name": "feed_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
valueYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that item.* pins are undoable via history, while channel.* keys and show mutate data shared by every episode, are persisted to the show file, and are not undone by history. That is exactly the kind of blast-radius information an agent needs before a write. It doesn't mention permissions or failure modes, so not a 5.

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?

Information density is high and the core action is front-loaded, but the backtick-heavy formatting and the trailing fragment 'Not ``add_chapter_tool``.' make it read as stitched-together notes rather than clean prose. Little is wasted, though the coercion and unset rules could be tighter.

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 single-field mutation with three parameters and an output schema (which removes any need to describe return values), the description covers valid key syntax, value typing, undo scope, and cross-episode side effects. The only material hole is project_path, plus absent guidance on error behavior for an invalid field key.

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 0%, so the description must compensate, and it does for two of three parameters: field is defined as a feed_read key with six concrete examples including the bracket-path form, and value is defined as text with explicit coercion rules (2 and "2" both set season 2) and the blank-text-unset convention. project_path is entirely undocumented in both schema and description, which keeps it from 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 precise verb+resource statement ('Pin one podcast-listing value') and immediately scopes it to a single field of a podcast listing. It distinguishes itself from feed_read (source of valid keys), feed_unset (implied inverse), and explicitly excludes add_chapter_tool, so an agent can route without opening other schemas.

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?

It gives concrete when-to guidance: use item.intro rather than item.notes for episode intros, blank text unsets, and chapters/clips/speakers/transcripts must be edited elsewhere. The one gap is that it never names feed_unset as the alternative for removing a pin, leaving that routing 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