FeedKeeper RSS/Atom reader and remote MCP Server

Export feeds as OPML XML

export_opml

Export all subscribed feeds and their folder structure as an OPML 2.0 XML file to back up, migrate, or share RSS/Atom subscriptions.

Instructions

Exports all subscribed feeds and folder structures of the current user as an OPML 2.0 XML document. Safe read-only operation.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.36.3Nov 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden; it does disclose that the operation is read-only and returns an XML document, which is valuable safety context. It does not mention size limits, whether unread state is preserved, or authentication requirements.

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?

Two short sentences, front-loaded with the action and output format. The 'Safe read-only operation' sentence is slightly redundant with the implicit nature of an export but does add signal given no annotations.

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

Completeness3/5

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

Adequate for a no-parameter tool with no output schema, but it leaves gaps an agent may need: whether import_opml round-trips the format and whether the response body is raw XML or wrapped.

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?

Zero parameters, so the baseline of 4 applies; the description usefully clarifies that the export scope is implicit (all subscribed feeds plus folder structure of the current user) rather than configurable.

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 (exports), resource (subscribed feeds and folder structures), and output format (OPML 2.0 XML), scoped to the current user. Easily distinguished from siblings like list_feeds or import_opml.

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?

Implies usage as a bulk export of subscriptions, with import_opml as the evident counterpart, but never explicitly says when to use it instead of list_feeds/list_folders or notes that it takes no filtering parameters.

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