Skip to main content
Glama
rss-mcp

rss-mcp

by huangcheng

import_opml

Import OPML feed subscriptions into the local RSS database, adding each feed while skipping URLs that already exist.

Instructions

Add each OPML feed. Existing URLs are skipped.

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

Input Schema

NameRequiredDescriptionDefault
opmlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: existing URLs are skipped rather than duplicated or errored. It omits whether feeds are also fetched/validated, what happens with malformed OPML, and whether the operation is additive and safe to repeat.

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 followed by the one non-obvious behavior. Nothing is wasted, though the extreme brevity leaves the missing parameter and procedural detail unaddressed rather than merely compact.

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 spelled out, but for a bulk mutation tool with an undocumented sole parameter and no annotations, the description stops short of telling an agent what to pass and what side effects to expect.

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 single parameter has 0% schema description coverage and the description never explains what the `opml` string must contain (raw OPML XML text vs. a file path or URL) or any size limits. The description should compensate for the undocumented parameter and largely does not.

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?

"Add each OPML feed" names a specific verb (add) and resource (OPML feeds), and the plural "each" signals a bulk import rather than a single subscription. It does not explicitly contrast with add_subscription, so an agent must infer the boundary, but the purpose itself is unambiguous.

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?

Usage is only implied: an agent can infer this is for importing a collection of feeds from OPML, but the description never says when to choose it over add_subscription or export_opml, nor whether it is the only path for bulk migration. No prerequisites or failure conditions are stated.

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