Skip to main content
Glama

List RSS / blog feeds

list_rss_feeds

List the RSS / blog feeds connected in Flomixy, each with its newest items (id, title, link, status new/drafted/ignored, postStatus). Use a feed id + item id (or the item link) with generate_posts_from_rss_item to turn a blog article into social posts. Requires scope ACCOUNTS_READ.

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_rss_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsPerFeedNoNewest items to return per feed (default 5, max 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and largely meets it: it declares this is a read/list operation, names the exact fields returned per item and the possible status values, and states the auth scope requirement. Remaining gaps are minor (no statement about feed ordering or rate limits).

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?

Two tight sentences: the first defines the resource and its payload, the second the follow-on action and prerequisite scope. No redundancy or filler, and the core purpose is front-loaded.

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, single-optional-parameter read tool with no output schema, the description supplies everything needed: what is returned, what the status values mean, the follow-on tool, and the required scope. Nothing an agent needs to invoke it correctly is missing.

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 single itemsPerFeed parameter already documents default 5 and max 20, so the description adds little. It only implies item limiting via "newest items" without restating bounds, which is acceptable given the schema, hence the baseline 3.

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?

States a specific verb and resource ("List the RSS / blog feeds connected in Flomixy") and goes further to enumerate the payload of each entry (id, title, link, status new/drafted/ignored, postStatus). An agent can distinguish this from siblings like list_posts or list_media purely from the text.

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?

Explicitly describes the follow-on workflow: take a feed id + item id (or item link) into generate_posts_from_rss_item to convert an article into social posts, and states the required scope ACCOUNTS_READ. It doesn't state when *not* to use it, but the usage context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources