Skip to main content
Glama
Podcast MCP
by calebn

feed_unset

Removes an episode or show pin from a field so it reverts to automatic values, including resetting values after feed_read reports a changed pin source.

Instructions

Drop this episode's pin on a listing value so it goes back to automatic.

Also how to take the new automatic value after feed_read reports a pin whose source changed. Unsetting a field that holds no pin changes nothing. An episode value undoes with history; a show value (channel.*) is dropped from the show and does not.

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>"
    },
    "name": "feed_unset"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

B3.2/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 discloses meaningful side effects: unsetting a field with no pin is a no-op, episode values undo with history, and show values (channel.*) are dropped from the show without history. It still omits permissions and error behavior, but the core mutation semantics are unusually well specified.

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 purpose is front-loaded, but the second sentence about taking the new automatic value after feed_read is confusingly worded and interrupts the flow. The remaining behavioral details are useful but could be structured more cleanly.

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?

For a two-parameter mutation tool with no annotations and zero schema description coverage, the definition is incomplete. It never explains the project_path parameter or provides enough field syntax to let an agent call the tool confidently without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 fully define both parameters. It only partially clarifies the field parameter by distinguishing episode values from show values (channel.*), and it never mentions the optional project_path parameter or its purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action: dropping this episode's pin on a listing value so it returns to automatic. It distinguishes the tool from a generic setter by naming the episode-level resource, though it does not explicitly contrast with feed_set or feed_write.

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

Usage Guidelines3/5

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

It provides a usage scenario after feed_read reports a pin whose source changed, which implies when to use the tool. However, there is no explicit when-not guidance and no direct comparison to feed_set, so the agent must infer the alternative.

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