Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_unstar

Idempotent

Remove the starred status from up to 100 FreshRSS articles by their IDs to organize or clear saved items.

Instructions

Unstar articles by id (at most 100).

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": {
      "ids": "<ids>"
    },
    "name": "freshrss_unstar"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is known. The description adds one genuinely new behavioral fact — the 100-id batch ceiling — but says nothing about what happens with unknown or already-unstarred ids, or whether partial failures are tolerated.

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?

A single front-loaded sentence with the resource first and the operational limit second; nothing is padded or restated from the title.

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 described, and annotations cover safety and idempotency. For a one-parameter tool the definition is nearly sufficient, with only failure handling for bad or duplicate ids left unaddressed.

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 must carry the parameter meaning; it does identify the ids as article ids and caps the array at 100. It does not explain that items are string-typed identifiers, whether order matters, or whether mixing invalid ids aborts the whole call.

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?

"Unstar articles by id" states a specific verb and resource, so an agent can immediately tell this is the inverse of freshrss_star without opening a schema. It stops short of explicitly naming that sibling or the feed/category scope it operates on.

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 parenthetical "at most 100" gives a concrete batching constraint that shapes how the tool is invoked, which is implicit usage guidance. There is no statement of when to prefer this over freshrss_star or freshrss_mark_unread, and no prerequisites or error conditions are mentioned.

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