Skip to main content
Glama
StripFeed

stripfeed-mcp-server

Official

batch_fetch

Fetches up to 10 URLs in parallel and converts each to clean, token-efficient Markdown. Strips ads, navigation, and scripts for AI agents.

Instructions

Fetch multiple URLs in parallel and convert them all to clean Markdown. Process up to 10 URLs in a single call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesArray of URLs to fetch (1-10)
modelNoAI model ID for cost tracking

Implementation Reference

  • The 'batch_fetch' tool handler: calls the /batch endpoint, processes results, and formats markdown output.
    server.tool(
      "batch_fetch",
      "Fetch multiple URLs in parallel and convert them all to clean Markdown. Process up to 10 URLs in a single call.",
      {
        urls: z
          .array(z.string().url())
          .min(1)
          .max(10)
          .describe("Array of URLs to fetch (1-10)"),
        model: z
          .string()
          .optional()
          .describe("AI model ID for cost tracking"),
      },
      async (params) => {
        const apiKey = getApiKey();
    
        const response = await fetch(`${BASE_URL}/batch`, {
          method: "POST",
          headers: {
            Authorization: `Bearer ${apiKey}`,
            "Content-Type": "application/json",
          },
          body: JSON.stringify({
            urls: params.urls,
            model: params.model,
          }),
        });
    
        if (!response.ok) {
          const body = await response.text();
          let message: string;
          try {
            message = JSON.parse(body).error;
          } catch {
            message = body;
          }
          throw new Error(`StripFeed API error ${response.status}: ${message}`);
        }
    
        const data = await response.json();
        const results = data.results as Array<{
          url: string;
          title: string;
          markdown: string;
          tokens: number;
          originalTokens: number;
          savingsPercent: number;
          status: number;
          error?: string;
        }>;
    
        const sections = results.map((r) => {
          if (r.status !== 200) {
            return `## ${r.url}\n\nError: ${r.error ?? `Status ${r.status}`}`;
          }
          const saved = `${r.tokens.toLocaleString()} tokens (saved ${r.savingsPercent}% from ${r.originalTokens.toLocaleString()})`;
          return `## ${r.title || r.url}\n\nSource: ${r.url} | ${saved}\n\n${r.markdown}`;
        });
    
        const summary = `Fetched ${data.success}/${data.total} URLs successfully.`;
    
        return {
          content: [
            { type: "text" as const, text: `${summary}\n\n---\n\n${sections.join("\n\n---\n\n")}` },
          ],
        };
      }
    );
  • The input schema for batch_fetch: takes an array of URLs (1-10) and an optional model string.
    server.tool(
      "batch_fetch",
      "Fetch multiple URLs in parallel and convert them all to clean Markdown. Process up to 10 URLs in a single call.",
      {
        urls: z
          .array(z.string().url())
          .min(1)
          .max(10)
          .describe("Array of URLs to fetch (1-10)"),
        model: z
          .string()
          .optional()
          .describe("AI model ID for cost tracking"),
      },
  • src/index.ts:162-163 (registration)
    Registration of the 'batch_fetch' tool on the MCP server via server.tool().
    server.tool(
      "batch_fetch",
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It mentions parallel processing and a limit of 10 URLs, but lacks details on error handling, authentication, rate limiting, or output format. Incomplete for a batch operation.

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?

Two sentences with no fluff. Front-loaded with the main action. Every sentence serves a purpose.

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 of batch fetching (parallel, multiple URLs, conversion), the description is insufficient. Missing details on output format, error propagation, and concurrency behavior. No output schema exists to compensate.

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 coverage is 100%, so the baseline is 3. The description does not add meaning beyond the schema; it only restates the parameters without extra context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Fetch', the resource 'multiple URLs', and the output 'clean Markdown'. It distinguishes from sibling 'fetch_url' by indicating parallel processing of multiple URLs.

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 on when to use this tool vs alternatives like fetch_url or check_usage. Does not specify when not to use it or any 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

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/StripFeed/mcp-server'

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