Skip to main content
Glama

fetchYoutube

Retrieve all videos from the Goose YouTube channel using Content Fetcher MCP to track content updates across sessions.

Instructions

Fetch ALL YouTube videos from the Goose channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that fetches YouTube videos from the specified channel using RSS parser and maps them to ContentItem objects.
    async function fetchYoutube(): Promise<ContentItem[]> {
      const feed = await rssParser.parseURL(
        `https://www.youtube.com/feeds/videos.xml?channel_id=${YOUTUBE_CHANNEL_ID}`
      );
    
      return feed.items.map((item) => ({
        id: item.id || item.link || "",
        title: item.title || "",
        url: item.link || "",
        published_at: item.pubDate || "",
        type: "video" as const,
      }));
    }
  • src/server.ts:133-138 (registration)
    Registration of the fetchYoutube tool with FastMCP server, including empty input schema and execution that calls the handler.
    server.addTool({
      name: "fetchYoutube",
      description: "Fetch ALL YouTube videos from the Goose channel.",
      parameters: z.object({}),
      execute: async () => JSON.stringify(await fetchYoutube()),
    });
  • Type definition for ContentItem used as output type for fetchYoutube and other fetch tools.
    interface ContentItem {
      id: string;
      title: string;
      url: string;
      published_at: string;
      type: "video" | "blog" | "release";
    }
  • Zod input schema for the tool (empty object, no parameters).
    parameters: z.object({}),
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 mentions fetching 'ALL' videos, implying a comprehensive retrieval, but lacks details on rate limits, authentication needs, pagination, or what the return format looks like (e.g., list of videos, metadata). This leaves significant gaps for an agent to understand how to handle the tool effectively.

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 front-loaded and wastes no space, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete for a tool that fetches content. It doesn't explain what is returned (e.g., video details, links, or raw data), potential errors, or behavioral aspects like rate limits. For a content retrieval tool with no structured support, 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.

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 adds no parameter information, which is acceptable here as there are no parameters to describe, aligning with the baseline expectation for zero-parameter tools.

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 target resource ('ALL YouTube videos from the Goose channel'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'fetchRss' or 'fetchGithubReleases', which might also retrieve content from different sources.

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 such as 'fetchRss' or 'fetchGooseBlog', nor does it mention any prerequisites or exclusions. It simply states what the tool does without context for selection.

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