FeedKeeper RSS/Atom reader and remote MCP Server

Mark articles as unread

mark_unread

Marks one or more subscribed RSS/Atom articles as unread by item ID, with single or batch updates to resurface items for later reading.

Instructions

Marks one or more subscribed articles as unread. Accepts a single itemId or an array of itemIds for batch processing. Idempotent. Returns { ok: true, updated: number } where updated is the count of items that actually transitioned to unread.

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

Input Schema

Name	Required	Description	Default
`itemId`	No	A single item ID to target
`itemIds`	No	An array of up to 200 item IDs to target in batch

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.36.4Nov 9, 2026

changedInput schema / properties / itemId / description

Previous value: -"A single item ID"New value: +"A single item ID to target"

changedInput schema / properties / itemIds / description

Previous value: -"Up to 200 item IDs"New value: +"An array of up to 200 item IDs to target in batch"

First observedv0.36.3Nov 9, 2026

TDQS

A3.8/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 declares idempotency, defines the return shape, and clarifies that 'updated' counts only items that actually transitioned. It stops short of describing behavior for invalid or non-subscribed IDs, or what happens if both itemId and itemIds are passed.

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?

Three short sentences, front-loaded with the action, then the accepted input forms, then the contract. No redundant restatement of the schema and no filler.

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?

Although no output schema exists, the description documents the return value itself, which is the key gap it needed to close. Remaining holes are edge cases: invalid IDs, non-subscribed items, and the zero-argument case given that no parameters are required.

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%, so the baseline is 3. The description adds the single-vs-batch distinction and ties 'updated' to the batch semantics, but does not clarify mutual exclusivity or precedence when both parameters are present.

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?

States a specific verb and resource ('Marks one or more subscribed articles as unread'), which is clearly distinguishable from mark_read and mark_all_read by scope. It never names those siblings, so the differentiation is inferred rather than explicit.

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?

The description explains the two calling modes (single itemId vs itemIds array for batch), which implies usage, but gives no explicit when-to-use/when-not guidance versus mark_read or mark_all_read. It also doesn't state that at least one of the two parameters must be supplied, despite both being optional in the schema.

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