Skip to main content
Glama
MissionSquad

@missionsquad/mcp-rss

Official

get_feed_headlines

Extract and format RSS feed headlines, including titles, summaries, and URLs, in markdown, text, HTML, or JSON. Simplify content retrieval for analysis or integration.

Instructions

Gets a list of headlines from a feed, including title, summary, and URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format for the headlinesjson
urlYesThe RSS feed URL to get headlines from

Implementation Reference

  • The execute handler function for the 'get_feed_headlines' tool. It fetches the RSS feed (using cache or rssReader), extracts and formats headlines based on the specified format (markdown, html, text, or json), and returns a structured JSON output with feed metadata and list of headlines.
    execute: async (args, context) => {
      logger.info(`Getting headlines from: ${args.url}`);
    
      // Fetch feed
      let feed: FeedResult | null = feedCache.get(args.url);
      if (!feed) {
        feed = await rssReader.fetchFeed(args.url);
        feedCache.set(args.url, feed);
      }
    
      // Format headlines
      const formatHeadline = (item: FeedItem) => {
        const headline = {
          title: item.title,
          summary: item.description || item.content,
          url: item.url,
          published: item.published,
          author: item.author,
        };
    
        switch (args.format) {
          case "markdown":
            return `### [${headline.title}](${headline.url})\n${headline.summary}`;
          case "html":
            return `<h3><a href="${headline.url}">${headline.title}</a></h3><p>${headline.summary}</p>`;
          case "text":
            return `${headline.title}\n${headline.summary}\n${headline.url}`;
          case "json":
          default:
            return headline;
        }
      };
    
      const headlines = feed.items.map(formatHeadline);
    
      const output = {
        feedTitle: feed.info.title,
        feedUrl: args.url,
        itemCount: feed.items.length,
        format: args.format,
        headlines,
      };
    
      logger.info(`Got ${headlines.length} headlines from ${args.url}`);
      return JSON.stringify(output, null, 2);
    },
  • Zod schema defining the input parameters for the 'get_feed_headlines' tool: required 'url' for the RSS feed and optional 'format' (default 'json') for output formatting.
    const GetFeedHeadlinesSchema = z.object({
      url: z.string().describe("The RSS feed URL to get headlines from"),
      format: z
        .enum(["markdown", "text", "html", "json"])
        .optional()
        .default("json")
        .describe("Output format for the headlines"),
    });
  • src/index.ts:452-503 (registration)
    Registration of the 'get_feed_headlines' tool with the FastMCP server, specifying name, description, input schema, and inline execute handler.
    server.addTool({
      name: "get_feed_headlines",
      description:
        "Gets a list of headlines from a feed, including title, summary, and URL.",
      parameters: GetFeedHeadlinesSchema,
      execute: async (args, context) => {
        logger.info(`Getting headlines from: ${args.url}`);
    
        // Fetch feed
        let feed: FeedResult | null = feedCache.get(args.url);
        if (!feed) {
          feed = await rssReader.fetchFeed(args.url);
          feedCache.set(args.url, feed);
        }
    
        // Format headlines
        const formatHeadline = (item: FeedItem) => {
          const headline = {
            title: item.title,
            summary: item.description || item.content,
            url: item.url,
            published: item.published,
            author: item.author,
          };
    
          switch (args.format) {
            case "markdown":
              return `### [${headline.title}](${headline.url})\n${headline.summary}`;
            case "html":
              return `<h3><a href="${headline.url}">${headline.title}</a></h3><p>${headline.summary}</p>`;
            case "text":
              return `${headline.title}\n${headline.summary}\n${headline.url}`;
            case "json":
            default:
              return headline;
          }
        };
    
        const headlines = feed.items.map(formatHeadline);
    
        const output = {
          feedTitle: feed.info.title,
          feedUrl: args.url,
          itemCount: feed.items.length,
          format: args.format,
          headlines,
        };
    
        logger.info(`Got ${headlines.length} headlines from ${args.url}`);
        return JSON.stringify(output, null, 2);
      },
    });
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. It states the tool 'Gets' data, implying a read-only operation, but does not disclose behavioral traits such as error handling, rate limits, authentication needs, or what happens with invalid URLs. For a tool with no annotation coverage, this leaves significant gaps.

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 that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action, resource, and data included.

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 the complexity (2 parameters, no annotations, no output schema), the description is incomplete. It lacks details on return values (e.g., structure of the list), error cases, or behavioral context, which are crucial for a tool with no structured output or annotation support.

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 both parameters ('url' and 'format') with details like enum values and defaults. The description adds no additional meaning beyond what the schema provides, such as explaining feed URL formats or format implications, meeting the baseline for high schema coverage.

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 verb ('Gets') and resource ('list of headlines from a feed'), specifying what data is included ('title, summary, and URL'). It distinguishes from siblings like 'extract_feed_content' or 'fetch_multiple_feeds' by focusing on headlines only, but could be more explicit about the differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'fetch_rss_feed' or 'search_feed_items'. The description implies usage for retrieving headlines from a single feed URL, but lacks explicit when/when-not instructions or prerequisites.

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

Related 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/MissionSquad/mcp-rss'

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