Skip to main content
Glama
mcp-for-dev

MCP Server for Google Search

by mcp-for-dev

read_webpage

Extract the main text content from any webpage by providing its URL. Returns clean, readable text without HTML or formatting, suitable for further analysis.

Instructions

Fetch and extract text content from a webpage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the webpage to read

Implementation Reference

  • The handler function that executes the read_webpage tool logic. Fetches a webpage via HTTP, parses HTML with cheerio, removes script/style elements, and extracts the title and body text.
    private async handleReadWebpage(url: string) {
        try {
            const response = await axios.get(url);
            const $ = cheerio.load(response.data);
    
            // Remove script and style elements
            $('script, style').remove();
    
            const content: WebpageContent = {
                title: $('title').text().trim(),
                text: $('body').text().trim().replace(/\s+/g, ' '),
                url: url,
            };
    
            return {
                content: [{
                    type: 'text',
                    text: JSON.stringify(content, null, 2),
                }],
            };
        } catch (error: unknown) {
            return {
                content: [{
                    type: 'text',
                    text: `Webpage fetch error: ${error instanceof Error ? error.message : String(error)}`,
                }],
                isError: true,
            };
        }
    }
  • The input schema and tool definition for read_webpage. Defines the tool name as 'read_webpage', provides a description, and specifies the input schema requiring a 'url' string parameter.
    const readToolSchema = {
        name: 'read_webpage',
        description: 'Fetch and extract text content from a webpage',
        inputSchema: {
            type: 'object',
            properties: {
                url: {
                    type: 'string',
                    description: 'URL of the webpage to read',
                },
            },
            required: ['url'],
        },
    };
  • src/index.ts:189-193 (registration)
    Where the read_webpage tool handler is invoked. In the CallToolRequestSchema handler, the code checks if the tool name is 'read_webpage', extracts the url argument, and calls handleReadWebpage.
    // Handle read_webpage tool
    if (request.params.name === 'read_webpage') {
        const {url} = request.params.arguments as { url: string };
        return await this.handleReadWebpage(url);
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only states basic purpose without mentioning rate limits, authentication, dynamic content handling, or error responses.

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?

Single sentence, front-loaded with action, no unnecessary words. Perfectly concise.

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?

For a simple tool with one parameter and no output schema, the description is adequate but lacks details on handling of large pages, timeouts, or what 'text content' entails (e.g., stripping HTML).

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% (single 'url' parameter described), so baseline is 3. The description adds no extra meaning beyond the schema, such as URL format or protocol support.

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?

Description clearly states the action ('Fetch and extract') and the resource ('text content from a webpage'), distinguishing it from sibling tool 'search' which is for querying.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. The sibling 'search' suggests a different purpose, but the description does not clarify contexts or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools