Skip to main content
Glama

List subscriptions

list_subscriptions
Read-onlyIdempotent

Retrieve RSS feed subscriptions with folders, URLs, and metadata. Filter by folder or search by title/URL, then paginate results to find and audit feeds.

Instructions

List RSS feed subscriptions with their folders, URLs, and metadata. Supports filtering by folder and searching by title/URL. Returns paginated results (default 100). 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": "list_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax subscriptions to return (default 100)
folderNoFilter to subscriptions in this folder name
offsetNoNumber of subscriptions to skip (default 0)
searchNoFilter by title or URL (case-insensitive substring match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.6.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max subscriptions to return (default 100)",
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Number of subscriptions to skip (default 0)",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Filter by title or URL (case-insensitive substring match)",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds genuinely useful operational context: pagination default of 100, cost of 1 Zone 1 request, retry accounting up to 4 attempts, honoring cached status/cooldown, and a pointer to inoreader://usage. The line about never replaying uncertain writes is boilerplate that does not apply to a read tool, which keeps this from a 5.

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?

Front-loaded with purpose and return contents, then filtering, then cost and limits, which is a sensible order with little redundancy. The trailing retry/write-replay sentence is irrelevant noise for a read-only listing and slightly dilutes focus.

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 usefully says what is returned and that results are paginated with a default of 100, and it discloses cost and rate-limit references. An agent has enough to call it correctly; only the choice among sibling listing tools remains underspecified.

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%, so each of the four parameters is already documented with type, bounds and meaning. The description restates the default page size and the existence of folder/search filtering but adds no format, matching rules or edge-case behavior beyond the schema, so the baseline 3 applies.

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 ("List RSS feed subscriptions") plus what is returned (folders, URLs, metadata), which clearly separates it from write-oriented siblings like manage_subscription and batch_edit_subscriptions. It does not explicitly name those alternatives, so it stops short of full sibling differentiation.

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?

It gives implied usage through the filter options (by folder, by title/URL), which tells the agent this is the browse/query entry point. However, it never says when to prefer this over list_folders_and_tags or get_uncategorized_feeds, nor any exclusions, leaving the routing decision partly to inference.

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