Skip to main content
Glama
Sign In

Lion Reader

by com.lionreader
OverviewDiscussionsAdmin

list_subscriptions

Read-only

List the user's active subscriptions: web feeds, newsletters, collections and (once they've saved an article) their Saved list, which can't be tagged, renamed or removed. Each has its id, title, type, tags and unread count. Use this to find the subscriptionId or collectionId other tools take. Returns items and nextCursor when there are more: pass it as cursor for the next page. With an ID already in hand, use get_subscription.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly show this kind: web feeds, newsletters, collections, or Saved
limitNoNumber of subscriptions per page (max 100)
queryNoCase-insensitive title search (substring matching)
tagIdNoFilter by tag ID
cursorNoPagination cursor from previous response
unreadOnlyNoOnly show feeds with unread items
uncategorizedNoOnly show subscriptions with no tags

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real context on top: the returned fields (id, title, type, tags, unread count), the pagination contract (`items`/`nextCursor`), and the immutability constraint on Saved. It does not cover ordering of results or behavior when filters combine, but that is a minor gap against otherwise strong disclosure.

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?

Four tight sentences that front-load the scope, then purpose, then return/pagination, then the alternative. Dense but nearly every clause carries information; the field enumeration could be trimmed slightly since the output is implied by the surrounding text.

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?

With 7 optional parameters and no output schema, the description supplies the two things the schema cannot: what a result looks like and how pagination is driven. Together with the sibling routing and the Saved-list caveat, nothing an agent needs to call this correctly is missing.

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 baseline is 3; the description earns an extra point by closing the loop between the return field `nextCursor` and the `cursor` parameter ("pass it as `cursor` for the next page"), which the schema alone cannot express. It does not explain how `type`, `unreadOnly`, and `uncategorized` interact, which keeps it below 5.

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?

Opens with a specific verb+resource ("List the user's active subscriptions") and enumerates exactly what counts: web feeds, newsletters, collections, and the Saved list. It explicitly separates itself from get_subscription, so an agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

Gives a positive use case ("Use this to find the subscriptionId or collectionId other tools take") and an explicit exclusion with the named alternative ("With an ID already in hand, use get_subscription"). It also warns that the Saved list can't be tagged, renamed, or removed, which pre-empts a likely misuse.

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

All Lion Reader toolsInspect
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