Skip to main content
Glama

Import OPML

import_opml
Idempotent

Imports RSS/Atom subscriptions from an OPML file or URL into the local feed database, with an optional limit on feeds.

Instructions

Import the subscriptions listed in an OPML document.

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": {
      "source": "<source>"
    },
    "name": "import_opml"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum feeds to import
sourceYesPath to an .opml/.xml file, or an http(s) URL

Output Schema

NameRequiredDescriptionDefault
okYes
failedNoURLs that could not be added
messageYes
skippedNoFeeds already stored
importedNoFeeds newly added

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the bar is lower, but the description adds essentially nothing beyond them. It does not mention that repeated imports will not create duplicates, that feeds may be fetched over the network from an HTTP URL, or what happens to feeds already present in the list.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity borders on under-specification rather than tightness.

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 and the input schema is fully described, so return values and parameter formats need not be explained here. However, for a mutating, network-capable import tool the description omits whether existing feeds are skipped and what a partial or failed import looks like, leaving the agent to rely on annotations and the output schema alone.

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?

Schema description coverage is 100%, so both 'source' (path or http(s) URL) and 'limit' (max feeds, default 100, max 500) are fully documented in the schema. The description adds no extra meaning about accepted formats, URL vs. path behavior, or how the limit interacts with existing subscriptions, so the baseline 3 applies.

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 states a specific verb ('Import') and resource ('the subscriptions listed in an OPML document'), which is enough for an agent to identify the operation. It does not explicitly distinguish itself from export_opml or add_feed, relying on the reader to infer the inverse relationship from names alone.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as add_feed for single subscriptions. The only usage signal is the implicit notion of importing from a document, which the agent must infer.

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