Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_edit_feed

Idempotent

Rename a feed and/or move it to a category; pass an empty category to move it to the default category.

Instructions

Rename a feed and/or move it to category (an empty string moves it to the default category). feed is the feed id, e.g. feed/12.

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": {
      "feed": "<feed>"
    },
    "name": "freshrss_edit_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYes
titleNo
categoryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, and idempotent=true, so the mutation/safety profile is covered. The description adds a genuinely useful behavior (empty string moves the feed to the default category) and the id format, but it never says whether omitted or null fields are left unchanged — the key behavioral question for a partial-update tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the mutation summary front-loaded and parenthetical detail placed where it belongs. No wasted wording, though the `feed` id example might sit more naturally in the schema.

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?

An output schema exists, so return values need not be explained, and the tool is low-complexity with only three flat parameters. The remaining meaningful gap is the null-versus-omitted semantics for `title` and `category`, which an agent about to call this would want.

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 0%, so the description carries the full burden. It documents `feed` (format: feed/12) and `category` (empty-string semantics) but never names the `title` parameter, only implying it via 'rename', and gives no guidance on explicit null versus omission.

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 pair: 'Rename a feed and/or move it to `category`.' That clearly distinguishes it from siblings such as freshrss_rename_category or freshrss_subscribe. It does not name any alternative tool explicitly, so it stops just short of a 5.

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 implied rather than stated: the tool edits an already-subscribed feed, with two optional mutations. There is no statement about when to prefer this over unsubscribing/resubscribing, nor what happens when both `title` and `category` are omitted.

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