Skip to main content
Glama

Export OPML

export_opml
Read-only

Write all saved RSS/Atom subscriptions to an OPML 2.0 document at a chosen path so feeds can be backed up or moved to another reader.

Instructions

Write every saved subscription to an OPML 2.0 document.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_opml"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoDestination file path for the OPML document (parent dirs created)feeds.opml

Output Schema

NameRequiredDescriptionDefault
okYes
pathYesWhere the OPML document was written
feedsNoFeeds written to the document
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description explicitly says 'Write every saved subscription' to a destination file path. Writing a file to disk is an environment mutation, so the description contradicts the annotation. The only additional context beyond the annotation is the OPML 2.0 format and 'every saved subscription' scope, which does not resolve the conflict.

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?

It is a single, front-loaded sentence with no filler. Every word contributes to purpose, scope, or output 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?

An output schema exists and the tool has only one optional parameter, so the description need not explain return values. However, it omits important behavior such as whether an existing file is overwritten, and its 'write' claim conflicts with the read-only annotation, leaving the agent with an inconsistent picture.

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%, and the schema already documents the 'path' parameter, its default, and that parent directories are created. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Write'), a precise resource ('every saved subscription'), and an output format ('OPML 2.0 document'). This clearly distinguishes it from import_opml and other feed-management siblings without needing to inspect the schema.

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 export intent is implied, but there is no explicit when-to-use guidance, no mention of prerequisites such as refreshing feeds first, and no stated alternatives. For a simple export tool this is minimally adequate rather than helpful.

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