Skip to main content
Glama

fetchRss

Retrieve all blog posts from any RSS feed URL to monitor content updates and track new publications.

Instructions

Fetch ALL blog posts from any RSS feed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesRSS feed URL

Implementation Reference

  • The core handler function for the fetchRss tool: fetches and parses the RSS feed from the given URL and maps each item to a ContentItem object.
    async function fetchRss(url: string): Promise<ContentItem[]> {
      const feed = await rssParser.parseURL(url);
    
      return feed.items.map((item) => ({
        id: item.guid || item.link || "",
        title: item.title || "",
        url: item.link || "",
        published_at: item.pubDate || "",
        type: "blog" as const,
      }));
    }
  • Input schema definition using Zod for the fetchRss tool, specifying the required 'url' parameter.
    parameters: z.object({
      url: z.string().describe("RSS feed URL"),
    }),
  • src/server.ts:141-148 (registration)
    Registration of the fetchRss tool on the FastMCP server instance, including name, description, input schema, and execution wrapper that calls the handler and stringifies the result.
    server.addTool({
      name: "fetchRss",
      description: "Fetch ALL blog posts from any RSS feed.",
      parameters: z.object({
        url: z.string().describe("RSS feed URL"),
      }),
      execute: async ({ url }) => JSON.stringify(await fetchRss(url)),
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool fetches ALL blog posts but doesn't describe return format, pagination, rate limits, error handling, or authentication needs. This leaves significant gaps for a tool with no annotation coverage.

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?

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, clearly stating the tool's core functionality without unnecessary elaboration.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list of posts, raw XML), error conditions, or behavioral traits like rate limits. For a tool with zero structured coverage, this leaves the agent under-informed.

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 the schema already documents the single 'url' parameter. The description adds no additional meaning beyond what the schema provides, such as URL format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the tool's purpose with a specific verb ('fetch') and resource ('ALL blog posts from any RSS feed'). It distinguishes from some siblings by specifying RSS feeds rather than GitHub releases, GooseBlog, or YouTube content, though it doesn't explicitly differentiate from isNewContent or markContentSeen.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer fetchRss over fetchGithubReleases, fetchGooseBlog, or fetchYoutube, nor does it indicate any prerequisites or exclusions for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EbonyLouis/content-fetcher-mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server