Skip to main content
Glama
manimohans

The Verge News MCP Server

by manimohans

search-news

Search for The Verge news articles by keyword to find relevant content from the past 30 days.

Instructions

Search for news articles from The Verge by keyword

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesKeyword to search for in news articles
daysNoNumber of days to look back (default: 30)

Implementation Reference

  • The main handler function for the 'search-news' tool. It fetches the latest news from The Verge RSS feed, filters articles by the specified number of days and keyword (in title or content), formats them into brief summaries (limited to 10 items), and returns the result as structured text content or an error response.
    async ({ keyword, days = 30 }) => {
      try {
        const allNews = await fetchVergeNews();
        const filteredByDate = filterNewsByDate(allNews, days);
        const filteredByKeyword = filterNewsByKeyword(filteredByDate, keyword);
        const formattedNews = formatNewsItems(filteredByKeyword);
        const newsText = formatNewsAsBriefSummary(formattedNews, 10); // Use brief summary format with limit of 10
        
        return {
          content: [
            {
              type: "text",
              text: `# The Verge - Search Results for "${keyword}"\n\n${newsText}`
            }
          ]
        };
      } catch (error) {
        console.error("Error in search-news:", error);
        return {
          content: [
            {
              type: "text",
              text: `Error searching news: ${error instanceof Error ? error.message : String(error)}`
            }
          ],
          isError: true
        };
      }
    }
  • Zod input schema defining the parameters for the 'search-news' tool: required 'keyword' string and optional 'days' number.
    {
      keyword: z.string().describe("Keyword to search for in news articles"),
      days: z.number().optional().describe("Number of days to look back (default: 30)")
    },
  • src/index.ts:219-225 (registration)
    MCP server tool registration call for 'search-news', specifying the tool name, description, and input schema. The handler function follows immediately after.
    server.tool(
      "search-news",
      "Search for news articles from The Verge by keyword",
      {
        keyword: z.string().describe("Keyword to search for in news articles"),
        days: z.number().optional().describe("Number of days to look back (default: 30)")
      },
  • Helper function used by the search-news handler to filter news items containing the keyword in title or content (case-insensitive).
    function filterNewsByKeyword(items: Parser.Item[], keyword: string) {
      const lowerKeyword = keyword.toLowerCase();
      
      return items.filter((item) => {
        const title = (item.title || "").toLowerCase();
        const content = (item.contentSnippet || item.content || "").toLowerCase();
        
        return title.includes(lowerKeyword) || content.includes(lowerKeyword);
      });
    }
  • Core helper function that fetches and parses the RSS feed from The Verge, returning the list of news items. Used by the search-news handler.
    async function fetchVergeNews() {
      try {
        const feed = await parser.parseURL(VERGE_RSS_URL);
        return feed.items;
      } catch (error) {
        console.error("Error fetching RSS feed:", error);
        throw new Error("Failed to fetch news from The Verge");
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions searching by keyword but lacks details on permissions, rate limits, pagination, or the format of returned articles. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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 directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits, usage guidelines, and output format, which are important for a search tool. It meets the minimum viable standard but has clear gaps.

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?

The schema description coverage is 100%, so the input schema already documents both parameters ('keyword' and 'days') clearly. The description adds no additional meaning beyond what the schema provides, such as examples or constraints, but the baseline score of 3 is appropriate since 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 ('Search') and resource ('news articles from The Verge by keyword'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'get-daily-news' or 'get-weekly-news', which might also retrieve news articles but with different time-based scopes.

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 sibling tools like 'get-daily-news' or 'get-weekly-news', nor does it specify scenarios where keyword-based searching is preferred over time-based retrieval, leaving the agent without clear usage context.

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/manimohans/verge-news-mcp'

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