Skip to main content
Glama

import_opml

Import RSS feed subscriptions from OPML XML content into FreshRSS to manage and organize your feed collection.

Instructions

Import subscriptions from OPML

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opmlYesOPML XML content to import

Implementation Reference

  • MCP tool registration and handler implementation for "import_opml". It invokes the client's importOpml method.
    server.registerTool(
      'import_opml',
      {
        description: 'Import subscriptions from OPML',
        inputSchema: importOpmlSchema,
      },
      wrapTool('import_opml', async (args: z.infer<typeof importOpmlSchema>) => {
        await client.feeds.importOpml(args.opml);
        return textResult('Imported OPML subscriptions.');
      })
    );
  • Actual implementation of the OPML import logic that communicates with the underlying HTTP client.
     * Import subscriptions from OPML.
     */
    async importOpml(opmlXml: string): Promise<void> {
      await this.http.postRaw('/reader/api/0/subscription/import', opmlXml);
    }
  • Zod schema definition for the "import_opml" tool inputs.
    export const importOpmlSchema = z
      .object({
        opml: z.string().min(1).describe('OPML XML content to import'),
      })
      .strict();
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to specify whether the import is additive or destructive (replaces existing subscriptions), how it handles duplicate feeds, or what the return value indicates.

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?

The four-word description is maximally concise and front-loaded with the verb and resource. While efficient, it arguably sacrifices necessary behavioral context in favor of brevity given the lack of annotations or output schema.

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?

For a data-import tool with no annotations and no output schema, the description provides minimal viable context by identifying the operation type and data format, but leaves significant gaps regarding conflict resolution, idempotency, and success/failure indicators.

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?

The input schema has 100% description coverage ('OPML XML content to import'), clearly indicating the parameter expects raw XML content rather than a file path. The tool description adds no additional parameter semantics, meeting the baseline expectation when the schema is self-documenting.

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?

The description uses a specific verb ('Import') and identifies both the resource ('subscriptions') and format ('OPML'), distinguishing it from single-feed siblings like 'subscribe' or 'quickadd_feed'. However, it stops short of explicitly clarifying that this is a bulk operation for multiple feeds.

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?

The description states what the tool does but provides no guidance on when to use this versus single-feed alternatives like 'subscribe' or 'quickadd_feed', nor does it mention prerequisites such as XML format requirements or size limitations.

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