Skip to main content
Glama

fetch_txt

Extract plain text content from any website by providing its URL. Removes HTML formatting for clean, readable output.

Instructions

Fetch a website, return the content as plain text (no HTML)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
headersNoOptional headers to include in the request
urlYesURL of the website to fetch

Implementation Reference

  • The core handler function for the 'fetch_txt' tool. Fetches the HTML, uses JSDOM to strip scripts/styles and extract body textContent, normalizes whitespace, and returns as plain text content.
    static async txt(requestPayload: RequestPayload) {
      try {
        const response = await this._fetch(requestPayload);
        const html = await response.text();
    
        const dom = new JSDOM(html);
        const document = dom.window.document;
    
        const scripts = document.getElementsByTagName("script");
        const styles = document.getElementsByTagName("style");
        Array.from(scripts).forEach((script) => script.remove());
        Array.from(styles).forEach((style) => style.remove());
    
        const text = document.body.textContent || "";
    
        const normalizedText = text.replace(/\s+/g, " ").trim();
    
        return {
          content: [{ type: "text", text: normalizedText }],
          isError: false,
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: (error as Error).message }],
          isError: true,
        };
      }
    }
  • src/index.ts:86-104 (registration)
    Registration of the 'fetch_txt' tool in the ListTools response, including name, description, and input schema.
    {
      name: "fetch_txt",
      description:
        "Fetch a website, return the content as plain text (no HTML)",
      inputSchema: {
        type: "object",
        properties: {
          url: {
            type: "string",
            description: "URL of the website to fetch",
          },
          headers: {
            type: "object",
            description: "Optional headers to include in the request",
          },
        },
        required: ["url"],
      },
    },
  • src/index.ts:140-143 (registration)
    Dispatch logic in CallToolRequestSchema handler that routes 'fetch_txt' calls to Fetcher.txt.
    if (request.params.name === "fetch_txt") {
      const fetchResult = await Fetcher.txt(validatedArgs);
      return fetchResult;
    }
  • Zod schema for request payload (url required, headers optional) used to validate and type inputs for all fetch tools, including fetch_txt.
    import { z } from "zod";
    
    export const RequestPayloadSchema = z.object({
      url: z.string().url(),
      headers: z.record(z.string()).optional(),
    });
    
    export type RequestPayload = z.infer<typeof RequestPayloadSchema>;
  • Private helper method for performing the actual HTTP fetch with custom User-Agent and error handling, used by all Fetcher methods including txt.
    private static async _fetch({
      url,
      headers,
    }: RequestPayload): Promise<Response> {
      try {
        const response = await fetch(url, {
          headers: {
            "User-Agent":
              "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36",
            ...headers,
          },
        });
    
        if (!response.ok) {
          throw new Error(`HTTP error: ${response.status}`);
        }
        return response;
      } catch (e: unknown) {
        if (e instanceof Error) {
          throw new Error(`Failed to fetch ${url}: ${e.message}`);
        } else {
          throw new Error(`Failed to fetch ${url}: Unknown error`);
        }
      }
    }
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 the action ('fetch') and output format, but lacks details on error handling, rate limits, authentication needs, timeouts, or what happens with non-text content. For a tool that performs network requests with no annotation coverage, this is a significant gap.

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 is front-loaded with the core purpose. Every word earns its place by specifying the action, resource, and output format without redundancy or unnecessary details.

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 (network fetch with 2 parameters), no annotations, and no output schema, the description is incomplete. It covers purpose and usage but lacks behavioral details like error handling or output structure. It meets minimal viability but has clear gaps for a tool with no structured 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 headers). The description does not add any meaning beyond what the schema provides, such as examples or constraints on URL formats or header usage. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific action ('fetch a website') and the resource ('website'), and distinguishes it from siblings by specifying the output format ('plain text (no HTML)'). This directly contrasts with fetch_html, fetch_json, and fetch_markdown, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool by specifying the output format ('plain text (no HTML)'), which inherently indicates when not to use it (e.g., when HTML, JSON, or Markdown is needed). This provides clear alternatives by naming the sibling tools implicitly through their output formats.

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/tokenizin-agency/mcp-npx-fetch'

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