Skip to main content
Glama

fetchGooseBlog

Retrieve all blog posts from Goose for content tracking and analysis within the Content Fetcher MCP server.

Instructions

Fetch ALL Goose blog posts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of fetching Goose blog posts via the generic RSS fetcher using the hardcoded RSS URL.
    async function fetchGooseBlog(): Promise<ContentItem[]> {
      return await fetchRss(GOOSE_BLOG_RSS);
    }
  • src/server.ts:151-156 (registration)
    Registration of the 'fetchGooseBlog' tool with FastMCP server, including name, description, empty input schema (z.object({})), and execute handler that calls the function and stringifies the result.
    server.addTool({
      name: "fetchGooseBlog",
      description: "Fetch ALL Goose blog posts.",
      parameters: z.object({}),
      execute: async () => JSON.stringify(await fetchGooseBlog()),
    });
  • TypeScript interface defining the structure of ContentItem objects returned by the fetchGooseBlog tool (output schema).
    interface ContentItem {
      id: string;
      title: string;
      url: string;
      published_at: string;
      type: "video" | "blog" | "release";
    }
  • Supporting helper function used by fetchGooseBlog to parse RSS feeds and map items to ContentItem format.
    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,
      }));
    }
  • Hardcoded RSS URL constant specifically used by the fetchGooseBlog handler.
    const GOOSE_BLOG_RSS = "https://block.github.io/goose/blog/rss.xml";
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Fetch ALL' but doesn't clarify whether this is a read-only operation, how it handles errors, if there are rate limits, or what the return format looks like. This leaves significant gaps for a tool that presumably retrieves data.

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 front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'Fetch ALL' entails (e.g., pagination, format of returned posts) or address behavioral aspects like error handling. Given the lack of structured data, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a high baseline score for not adding unnecessary information.

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 action ('Fetch') and resource ('ALL Goose blog posts'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'fetchRss' or 'fetchYoutube' that might also fetch content, so it misses the highest score.

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 like 'fetchRss' or 'isNewContent'. It lacks context about prerequisites, timing, or exclusions, leaving the agent with minimal usage direction.

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