Skip to main content
Glama
fetchSERP

FetchSERP MCP Server

Official
by fetchSERP

scrape_webpage

Extract raw webpage content without JavaScript execution using the FetchSERP MCP Server, enabling precise web scraping for SEO, data analysis, or keyword research tasks.

Instructions

Scrape a web page without JS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe url to scrape

Implementation Reference

  • Handler implementation for the 'scrape_webpage' tool. It calls the makeRequest method with the specific API endpoint '/api/v1/scrape' using GET method and the provided arguments.
    case 'scrape_webpage':
      return await this.makeRequest('/api/v1/scrape', 'GET', args, null, token);
  • Input schema definition for the 'scrape_webpage' tool, including name, description, and required 'url' parameter.
    name: 'scrape_webpage',
    description: 'Scrape a web page without JS',
    inputSchema: {
      type: 'object',
      properties: {
        url: {
          type: 'string',
          description: 'The url to scrape',
        },
      },
      required: ['url'],
    },
  • index.js:250-262 (registration)
    Registration of the 'scrape_webpage' tool in the ListTools response, defining its metadata and schema.
    {
      name: 'scrape_webpage',
      description: 'Scrape a web page without JS',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'The url to scrape',
          },
        },
        required: ['url'],
      },
  • Helper method 'makeRequest' used by the scrape_webpage handler to perform authenticated HTTP requests to the FetchSERP API.
    async makeRequest(endpoint, method = 'GET', params = {}, body = null, token = null) {
      const fetchserpToken = token || process.env.FETCHSERP_API_TOKEN;
      
      if (!fetchserpToken) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          'FETCHSERP_API_TOKEN is required'
        );
      }
    
      const url = new URL(`${API_BASE_URL}${endpoint}`);
      
      // Add query parameters for GET requests
      if (method === 'GET' && Object.keys(params).length > 0) {
        Object.entries(params).forEach(([key, value]) => {
          if (value !== undefined && value !== null) {
            if (Array.isArray(value)) {
              value.forEach(v => url.searchParams.append(`${key}[]`, v));
            } else {
              url.searchParams.append(key, value.toString());
            }
          }
        });
      }
    
      const fetchOptions = {
        method,
        headers: {
          'Authorization': `Bearer ${fetchserpToken}`,
          'Content-Type': 'application/json',
        },
      };
    
      if (body && method !== 'GET') {
        fetchOptions.body = JSON.stringify(body);
      }
    
      const response = await fetch(url.toString(), fetchOptions);
      
      if (!response.ok) {
        const errorText = await response.text();
        throw new McpError(
          ErrorCode.InternalError,
          `API request failed: ${response.status} ${response.statusText} - ${errorText}`
        );
      }
    
      return await response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'without JS' which indicates a behavioral trait (no JavaScript execution), but doesn't disclose other important behaviors: whether it follows redirects, handles authentication, respects robots.txt, has rate limits, returns structured data vs. raw HTML, or error conditions. For a scraping tool with zero 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 extremely concise (4 words) and front-loaded with the core functionality. Every word earns its place: 'Scrape' defines the action, 'a web page' specifies the target, and 'without JS' adds crucial behavioral context. No wasted words or redundant information.

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 this is a scraping tool with no annotations, no output schema, and multiple sibling scraping tools, the description is incomplete. It doesn't explain what gets returned (HTML content? structured data?), error handling, limitations, or how it differs from other scraping tools beyond the JS aspect. For a tool in this context, more completeness is needed.

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?

The description doesn't mention parameters at all. However, schema description coverage is 100% (the single 'url' parameter is fully documented in the schema), so the baseline is 3. The description adds no additional parameter context beyond what's already in the structured schema.

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 tool's purpose: 'Scrape a web page without JS' specifies the verb (scrape), resource (web page), and a key constraint (without JavaScript execution). It distinguishes from sibling 'scrape_webpage_js' by explicitly contrasting the JavaScript handling approach, though it doesn't mention other scraping alternatives like 'scrape_domain'.

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 context by stating 'without JS', suggesting this tool is for static HTML scraping when JavaScript rendering isn't needed. However, it doesn't explicitly state when to use this vs. 'scrape_webpage_js' or 'scrape_domain', nor does it mention any prerequisites or exclusions. The guidance is present but incomplete.

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/fetchSERP/fetchserp-mcp-server-node'

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