Skip to main content
Glama

OPML subscription export

bpj_opml_feed_subscriptions
Read-onlyIdempotent

Export feed names and XML feed URLs as an escaped OPML 2.0 subscription outline.

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": {
      "name": "<name>",
      "feeds": "<feeds>"
    },
    "name": "bpj_opml_feed_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
feedsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the format trait that output is an escaped OPML 2.0 outline; it says nothing about how escaping is performed, how malformed input is handled, or whether the result is returned inline or as a file.

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 the verb first and the output format last; no filler or redundant restatement of the title. It is arguably too terse rather than too long, but nothing in it is wasted.

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 two-parameter, non-destructive export with no output schema, the definition covers what is produced but not how the caller should format `feeds` entries or what `name` controls. Since there is no output schema, a sentence on the returned payload would have closed the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it only partly does. It hints at the paired "Name|feed URL" structure of the `feeds` parameter but never explains the delimiter between entries (relevant to the 3000-char cap), and the required `name` parameter — presumably the OPML title — is not mentioned at all.

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 names a specific verb ("Export") and resource (feed names and XML feed URLs) and states the output artifact (an escaped OPML 2.0 subscription outline). It does not explicitly contrast with a sibling, but among the listed siblings none is a competing subscription-export path, so the purpose is unambiguous on its own.

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 or when-not-to-use guidance and no named alternative. The agent must infer that this is the tool for producing OPML from the fact that it says "OPML 2.0"; nothing in the text routes it against another tool or states prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.