FeedKeeper RSS/Atom reader and remote MCP Server

Add a muted keyword filter

add_muted_keyword

Adds a case-insensitive keyword filter rule to suppress articles whose title or summary contains the keyword from feeds and editions.

Instructions

Adds a new keyword filter rule. Articles whose title or summary contains this keyword (case-insensitive) will be suppressed from feeds and editions. Requires write scope. Returns the created keyword rule { id, keyword, created_at }.

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": {
      "keyword": "<keyword>"
    },
    "name": "add_muted_keyword"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	Yes	The keyword phrase to filter out from feeds and editions (1 to 100 characters)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.36.4Nov 9, 2026
- addedInput schema / properties / keyword / description
```
Added value: +"The keyword phrase to filter out from feeds and editions (1 to 100 characters)"
```
First observedv0.36.3Nov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the case-insensitive suppression behavior, the required write scope, and the returned object shape, though it does not cover duplicate handling, idempotency, or error behavior.

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?

The description is three tight sentences with the core effect front-loaded, followed by permission and return details. Every sentence adds useful information without repetition.

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 simple one-parameter mutation tool with no output schema, the description provides the effect, scope requirement, and return shape. It is nearly complete, with minor gaps around duplicate handling and whether adding an existing keyword causes an error.

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 100%, so the schema already defines the keyword parameter. The description adds meaningful semantics by explaining that the keyword is matched case-insensitively against article titles and summaries.

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 states a specific verb and resource: adding a muted keyword filter rule. It also explains the effect, suppression from feeds and editions, which clearly distinguishes it from siblings like list_muted_keywords and unmute_keyword.

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 intended use is clear from the purpose, but there is no explicit when-to-use guidance, no exclusion cases, and no direct comparison to alternatives such as unmute_keyword. The agent can infer usage, but guidance is only implied.

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