Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_import_opml

Destructive

Import feed subscriptions from OPML text into FreshRSS to restore or migrate feeds in bulk. Requires confirm=true to apply changes.

Instructions

Import subscriptions from OPML text (at most 1 MB). Requires confirm=true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "opml": "<opml>"
    },
    "name": "freshrss_import_opml"
  }
}

Input Schema

NameRequiredDescriptionDefault
opmlYes
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare destructive=true, idempotent=false and openWorld=true, and the description adds two facts the annotations do not carry: a 1 MB size ceiling on the input and a mandatory confirm=true gate. It stops short of saying whether the import merges with or replaces existing subscriptions, which is the key destructive-behavior question.

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 short clauses, the action first and the constraints second, with no filler. Every element carries information an agent needs before calling.

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?

An output schema exists so return values need not be explained, and the size and confirmation constraints are covered. However, for a destructive, non-idempotent bulk operation, the description leaves unstated whether existing feeds are merged, duplicated, or overwritten.

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?

Schema description coverage is 0%, so the description has to carry the parameters, and it does: 'opml' is constrained to text up to 1 MB, and 'confirm' is stated as a required true value despite its default of false. That is meaningful compensation for the bare schema, missing only a note on what happens when confirm is false/omitted.

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: importing subscriptions from OPML text. It is immediately distinguishable from freshrss_export_opml and from single-feed freshrss_subscribe, though it does not explicitly name those alternatives.

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?

The OPML-input framing implies the use case (bulk migration/restore from an OPML file), but there is no explicit when-to-use versus when-not guidance and no pointer to freshrss_subscribe for adding a single feed.

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