Skip to main content
Glama

fetch_feed

Read-onlyIdempotent

Fetch and parse RSS 2.0 or Atom 1.0 feeds to retrieve feed metadata and entries, auto-detecting format for AI assistants processing syndicated content.

Instructions

Fetch and parse an RSS 2.0 or Atom 1.0 feed. Returns feed-level metadata (title, description, link, updated) plus a list of entries (title, link, id, published, updated, author, summary, content, contentType, categories). Auto-detects RSS vs Atom.

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": "fetch_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
limitNoMax entries to return (default 50)
max_bytesNoMax bytes to read (default 10MiB). A feed over 16 MiB is refused whatever max_bytes says.
timeout_msNo
user_agentNo
max_redirectsNo
allow_private_hostsNoAllow loopback / private / link-local targets for this call (default false). Refused unless the server operator launched fetch-mcp with FETCH_MCP_ALLOW_PRIVATE_HOSTS=1 -- SSRF protection stays on by default either way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.6
    • changedInput schema / properties / max_bytes / description
      Previous value: -"Max bytes to read (default 10MiB)"New value: +"Max bytes to read (default 10MiB). A feed over 16 MiB is refused whatever max_bytes says."
  2. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / allow_private_hosts / description
      Added value: +"Allow loopback / private / link-local targets for this call (default false). Refused unless the server operator launched fetch-mcp with FETCH_MCP_ALLOW_PRIVATE_HOSTS=1 -- SSRF protection stays on by default either way."
  3. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so safety is covered; the description adds valuable behavior beyond that by enumerating the exact returned structure and noting RSS/Atom auto-detection. It omits fetch-failure behavior, whether a malformed feed errors or returns partial data, and whether entries beyond the limit are silently dropped.

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 sentences, no filler: what it does first, what it returns second. The long field enumeration is justified because there is no output schema to carry it.

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?

With no output schema, the explicit return-shape listing is exactly what's needed, and the format detection detail closes a real ambiguity. Remaining gaps are the undocumented transport parameters and any statement about error conditions or truncation semantics.

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 only 43%, and the description mentions no parameter at all — it never explains that `limit` truncates the entries list or how `timeout_ms`, `max_redirects`, and `user_agent` affect the fetch. The parameters that most need documentation (max_bytes cap, private-host SSRF gate) are already documented in the schema, which keeps this at an adequate baseline rather than failing.

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?

States a specific verb+resource pair ('Fetch and parse an RSS 2.0 or Atom 1.0 feed') and adds that format detection is automatic, which cleanly separates it from the HTML/sitemap/reader siblings whose purpose is scraping markup rather than syndication feeds.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The format restriction implies the usage context clearly enough that an agent can pick it for feeds over the HTML-oriented siblings, but it never names an alternative or states an exclusion (e.g. 'use fetch_reader for article pages', 'use fetch_sitemap for sitemaps').

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