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);
    }
Behavior3/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. It discloses the basic action (fetch and extract text) but does not mention potential limitations like JavaScript execution, timeouts, or content size limits. For a simple tool, this is adequate but not thorough.

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 sentence that is concise and to the point, with no unnecessary words. It efficiently conveys the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema, no nested objects), the description is largely complete. It explains the input and the intended output. A minor addition could be mentioning that only text content is extracted, but it is not essential.

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% for the single parameter 'url,' and the description adds no further semantic information beyond what the schema already provides. Thus, it meets the baseline.

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 tool's function: 'Fetch and extract text content from a webpage.' It uses a specific verb and resource, and it clearly distinguishes from the sibling tool 'google_search,' which performs a different task.

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?

The description implies usage (read a specific webpage) but does not explicitly state when to use this tool versus the sibling 'google_search' or when not to use it. No alternative tools or exclusions are mentioned.

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/mcp-for-dev/mcp-google-search'

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