Skip to main content
Glama

Add feed

add_feed
Idempotent

Subscribe to an RSS/Atom feed and store its current items in SQLite. Re-adding a saved feed refreshes it instead of creating duplicates.

Instructions

Subscribe to an RSS/Atom feed, store it in SQLite and keep its current items.

Adding an already-saved feed refreshes it instead of duplicating it.

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_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFeed URL, or a site URL when auto_discover finds the feed
titleNoOptional display title overriding the feed's own title
auto_discoverNoIf the URL returns HTML, look for a <link rel='alternate'> feed URL

Output Schema

NameRequiredDescriptionDefault
okYes
feedNoState of the feed after the call
messageYesHuman-readable summary of what happened
new_entriesNoEntries inserted by this call
discovered_fromNoHTML page the feed URL was auto-discovered on, if any
removed_entriesNoEntries deleted together with the feed

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?

Annotations already declare idempotentHint=true, openWorldHint=true, destructiveHint=false, and readOnlyHint=false, so the safety and idempotency profile is supplied structurally. The description adds that items are persisted to SQLite and current items are kept, which hints at a network fetch and local write, but it does not cover failure modes (unreachable feed, invalid URL) or whether repeated adds re-fetch entries. Modest added value beyond annotations.

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, front-loaded with the primary action and side effects, then the idempotency nuance. No filler or redundant restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover safety and openness, so the description need not explain return values. It covers action, storage, and duplicate behavior adequately. Minor gaps remain around failure behavior and network/permission requirements for a tool with openWorldHint=true.

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 url, title, and auto_discover are already documented with defaults and meaning in the schema. The description adds no parameter-level detail, such as when auto_discover should be disabled. Baseline 3 applies when the schema carries the parameter burden.

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 (subscribe to an RSS/Atom feed) plus the side effects: stored in SQLite, current items retained. It also clarifies that re-adding an existing feed refreshes rather than duplicates, which distinguishes it from a plain duplicate-creation tool. It stops short of naming refresh_feed or import_opml as explicit alternatives.

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 second sentence gives a concrete re-use condition (adding an already-saved feed refreshes it), which is useful when-to-use guidance. However, there is no guidance on when to prefer refresh_feed, import_opml, or what to do if the URL is not a feed. Usage is implied rather than fully directed.

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