FeedKeeper RSS/Atom reader and remote MCP Server

Update feed settings

update_feed

Modify a feed subscription's display name, poll interval, full-text policy, notifications, badge counting, or moved URL. Returns the updated subscription record.

Instructions

Updates subscription settings for a feed: custom display name, poll interval, full-text extraction policy, push notification preference, badge counter inclusion, or updates the feed URL if the publisher relocated. Returns the updated subscription record.

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": {
      "feedId": "<feedId>"
    },
    "name": "update_feed"
  }
}

Input Schema

Name	Required	Description
`url`	No	New feed URL or website URL if the feed moved (auto-discovered and validated)
`badge`	No	Whether to count unread articles from this feed in the app icon badge number
`label`	No	Custom display name; pass null or empty string to restore the original feed title
`feedId`	Yes	The numeric ID of the subscribed feed to update
`notify`	No	Whether to send push notifications to user devices when new articles arrive
`fullText`	No	'auto' allows the reader to fetch full articles; 'never' always retains the feed content
`pollIntervalMinutes`	No	Poll interval in minutes (subject to server minimum)

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.36.4Nov 9, 2026

changedInput schema / properties / badge / description

Previous value: -"Count this feed's unread articles in the number on the app icon"New value: +"Whether to count unread articles from this feed in the app icon badge number"

addedInput schema / properties / feedId / description

Added value: +"The numeric ID of the subscribed feed to update"

changedInput schema / properties / fullText / description

Previous value: -"auto: the reader may fetch full articles; never: always show the feed content"New value: +"'auto' allows the reader to fetch full articles; 'never' always retains the feed content"

changedInput schema / properties / label / description

Previous value: -"Custom display name; null or empty restores the feed title"New value: +"Custom display name; pass null or empty string to restore the original feed title"

changedInput schema / properties / notify / description

Previous value: -"Send push notifications to the user's devices when this feed has new articles"New value: +"Whether to send push notifications to user devices when new articles arrive"

addedInput schema / properties / pollIntervalMinutes / description

Added value: +"Poll interval in minutes (subject to server minimum)"

changedInput schema / properties / url / description

Previous value: -"New feed URL or website URL (the feed is auto-discovered)"New value: +"New feed URL or website URL if the feed moved (auto-discovered and validated)"

First observedv0.36.3Nov 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the return value ("Returns the updated subscription record") and the relocating-URL scenario, but says nothing about permissions, whether the update is immediate/reversible, side effects of changing pollIntervalMinutes, or what happens when feedId is not a subscribed feed.

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?

Two sentences, zero filler, with the capability enumeration front-loaded ahead of the return-value note. Nothing could be cut without losing scope information.

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 seven-parameter mutation tool with full schema documentation, the description covers scope and the return value adequately. The remaining gap is preconditions and failure behavior, which matters more here because there are no annotations to signal safety.

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 coverage is 100%, so each of the seven parameters is already documented, including enum meaning and null-restore semantics for label. The description mostly restates those field names; its only real addition is the framing that the url parameter exists for publisher relocations, which the schema also mentions.

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?

Opens with a specific verb and resource ("Updates subscription settings for a feed") and then enumerates exactly which settings, which lets an agent separate it from refresh_feed, move_feed_to_folder, or subscribe_feed without consulting the schema. The relocation clause further disambiguates the URL case.

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?

Usage is only implied by the field list; there is no explicit "use this when..." or "use X instead". One implicit hint exists — updating the URL is framed as the response to a publisher relocation — but the description never says whether a forced refresh should be done via refresh_feed or that the feed must already be subscribed.

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