FeedKeeper RSS/Atom reader and remote MCP Server

Unsubscribe from a feed

unsubscribe_feed

Unsubscribe the authenticated user from a feed using its numeric feed ID; other feeds and users' subscriptions remain unaffected.

Instructions

Unsubscribes the current user from a feed by its feed ID. Destructive action. Feeds and other users' subscriptions are unaffected. Returns { ok: true } on success.

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

Input Schema

Name	Required	Description	Default
`feedId`	Yes	The numeric ID of the feed to unsubscribe from

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.36.4Nov 9, 2026
- addedInput schema / properties / feedId / description
```
Added value: +"The numeric ID of the feed to unsubscribe from"
```
First observedv0.36.3Nov 9, 2026

TDQS

A4/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 meaningful work: it flags 'Destructive action', bounds the blast radius ('Feeds and other users' subscriptions are unaffected'), and discloses the success shape ('Returns { ok: true }'). It stops short of stating whether the subscription can be restored or what happens to read/bookmark state on that feed, which is the remaining gap for a destructive operation.

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?

Four short sentences, front-loaded with the action and the identifier, then the destructive flag, the scope caveat, and the return value. Nothing is redundant and every sentence earns its place.

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 one-parameter mutation with no output schema, the description supplies the return value inline and constrains the effect to the current user. It is nearly complete; only the irreversibility/recovery story is left unstated.

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 description coverage is 100% — the single feedId parameter is already documented as 'The numeric ID of the feed to unsubscribe from'. The description's 'by its feed ID' restates that without adding format, sourcing, or error semantics 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?

States a specific verb and resource ('Unsubscribes the current user from a feed') plus the identifier scope ('by its feed ID'). It is unambiguously the inverse of subscribe_feed, so an agent can route between the pair without opening either schema.

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: the name and the phrase 'the current user' make clear it applies to the caller's own subscription, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. delete_folder or subscribe_feed). Adequate but leaves routing to inference.

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