Skip to main content
Glama
Sign In
inoreader-mcp

inoreader-mcp

by justmytwospence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get uncategorized feeds

get_uncategorized_feeds
Read-onlyIdempotent

Retrieves feeds that have no folder assignment as compact [stream_id, title] tuples so you can identify uncategorized feeds and assign them to folders.

Instructions

Get feeds that have no folder assignment, returned as compact [stream_id, title] tuples. Use this to identify feeds needing categorization, then call categorize_feeds with your assignments. Costs 1 Zone 1 request. Base costs exclude safe-read retries (up to 4 attempts, each counted); honor cached status/cooldown. Never blindly replay uncertain writes. See inoreader://usage for limits, URI examples and prompts.

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

Input Schema

NameRequiredDescriptionDefault
include_urlNoInclude site URL as a third tuple element (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description adds cost information, retry-counting behavior, cached status/cooldown guidance, and a warning about replaying uncertain writes. It also discloses the default tuple return format.

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?

The description is front-loaded with purpose and return format, then usage, cost, and retry guidance. It is efficient overall, though the generic warning about uncertain writes is slightly less relevant for a read-only getter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter, full schema coverage, and rich annotations, the description is complete. It covers purpose, return shape, next action, cost, retry behavior, and where to find limits.

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 coverage is 100%, and the schema already explains that include_url adds the site URL as a third tuple element. The description reinforces the default two-element tuple shape but adds little parameter meaning 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?

The description states a specific verb and resource: feeds with no folder assignment, and it specifies the return shape as compact [stream_id, title] tuples. It also distinguishes the tool's role by naming categorize_feeds as the follow-up action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: use this to identify feeds needing categorization, then call categorize_feeds with assignments. It does not explicitly state when not to use it or name every relevant alternative, but the workflow guidance is clear.

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

Deploy Server

Other Tools