Inoreader MCP Server and API by Cotlet

List subscriptions in Inoreader

inoreader_list_subscriptions

Read-onlyIdempotent

List subscriptions in the user's own Inoreader account from ChatGPT, Claude or any AI agent. Returns how to do it in Inoreader step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Inoreader Cloud Browser. Inoreader's official API: Inoreader has a REST API with OAuth 2.0 but no official MCP server (checked 27 Oct 2026).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: it performs no action itself and hands off to browser tools, and it notes the official API/OAuth situation. That is useful beyond the structured fields, though the handoff mechanics could be spelled out more.

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

Conciseness3/5

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

The core behavior is front-loaded, but the text wanders into audience framing ("from ChatGPT, Claude or any AI agent") and API trivia with a checked-on date that does not help an agent decide or invoke. Trimming those would sharpen it considerably.

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?

With no output schema, the description carries the burden of describing returns, and it does so at a high level ("screens, buttons, fields"). Combined with the explicit handoff to cotlet_browser_* tools, an agent has enough to act, though the exact shape of the returned guidance is only loosely characterized.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly implies no inputs are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 ("List subscriptions in the user's own Inoreader account"), but then immediately reframes the tool as returning step-by-step instructions rather than the subscriptions themselves. That tension between the name/title and the actual behavior leaves an agent unsure whether this tool lists data or produces a how-to guide.

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 a clear follow-on path: the tool "opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Inoreader Cloud Browser." That is actionable routing. It lacks any explicit when-not-to-use or comparison against the other inoreader_* siblings, which keeps it below a 5.

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

All Inoreader MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?