Skip to main content
Glama
rss-mcp

rss-mcp

by huangcheng

add_subscription

Add an RSS or Atom feed by URL to start tracking its entries; submitting the same URL returns the existing subscription instead of creating a duplicate.

Instructions

Add a feed by URL. Repeating a URL returns the existing subscription.

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": {
      "url": "<url>"
    },
    "name": "add_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
tagsNo
titleNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose one important trait, that repeating a URL returns the existing subscription rather than erroring or duplicating, which is genuinely useful. However it says nothing about whether the feed is fetched immediately, what errors occur for invalid URLs, or whether tags/title are persisted on repeat calls.

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 sentences with zero filler, and the core action is front-loaded before the idempotency caveat. Nothing could be removed without losing meaning.

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 needn't be explained, and the tool is simple enough that the short description mostly suffices. The gap is the unaddressed tags and title parameters and the absence of any behavioral context that annotations would otherwise supply.

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?

No enumerations and only three simple parameters, so the schema is largely self-explanatory; the description reinforces that url is the key input via 'Add a feed by URL.' It omits any mention of the optional tags and title parameters, leaving their purpose to the bare schema property names.

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: 'Add a feed by URL.' This clearly contrasts with siblings like remove_subscription, list_subscriptions, and import_opml without needing to name them. It stops short of explicitly differentiating from import_opml, which also adds subscriptions in bulk.

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 implied by 'Add a feed by URL,' and the idempotency note hints at when repeating a call is safe, but there is no explicit guidance on when to prefer import_opml for bulk additions or how this differs from fetch_feed. An agent must infer the boundaries.

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