Skip to main content
Glama

export_opml

Export all RSS feed subscriptions from FreshRSS in OPML format for backup or migration to other feed readers.

Instructions

Export all subscriptions as OPML

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'export_opml' tool handler.
    server.registerTool(
      'export_opml',
      {
        description: 'Export all subscriptions as OPML',
        inputSchema: exportOpmlSchema,
      },
      wrapTool('export_opml', async () => {
        const opml = await client.feeds.exportOpml();
        return textResult(opml);
      })
    );
  • The actual service method implementation that fetches the OPML data via HTTP.
    async exportOpml(): Promise<string> {
      return this.http.getText('/reader/api/0/subscription/export');
    }
  • Schema definition for the 'export_opml' tool input.
    export const exportOpmlSchema = z.object({}).strict();
Behavior2/5

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

No annotations provided, so description carries full burden. Specifies output format (OPML) but fails to disclose return type (file content, download URL, or file path), idempotency, or whether operation is read-only.

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?

Extremely concise at 6 words. No redundant text; every word conveys essential information (action, scope, format).

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 simple export tool but lacks output specification due to missing output schema. Without annotations or return value description, agent cannot predict response structure.

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 present. Per scoring rules, 0 params baseline is 4. Description correctly implies no filtering is possible via 'all subscriptions'.

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?

Clear verb (Export) and resource (all subscriptions) with specified format (OPML). Scope ('all') is explicit and matches the parameterless schema. Distinguishes directionally from sibling import_opml, though doesn't explicitly mention RSS/Atom context.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance or comparison to alternatives like import_opml or list_feeds. Doesn't indicate typical use cases (backup, migration, etc.).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alysson-souza/freshrss-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server