Skip to main content
Glama
fetchSERP

FetchSERP MCP Server

Official
by fetchSERP

scrape_webpage_js

Extract data from web pages by executing custom JavaScript scripts on the desired URL. Ideal for dynamic content scraping and tailored data retrieval tasks.

Instructions

Scrape a web page with custom JS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
js_scriptYesThe javascript code to execute on the page
urlYesThe url to scrape

Implementation Reference

  • Input schema definition for the 'scrape_webpage_js' tool, specifying required parameters 'url' and 'js_script'.
    {
      name: 'scrape_webpage_js',
      description: 'Scrape a web page with custom JS',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'The url to scrape',
          },
          js_script: {
            type: 'string',
            description: 'The javascript code to execute on the page',
          },
        },
        required: ['url', 'js_script'],
      },
    },
  • index.js:284-301 (registration)
    Registration of the 'scrape_webpage_js' tool in the listTools response.
    {
      name: 'scrape_webpage_js',
      description: 'Scrape a web page with custom JS',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'The url to scrape',
          },
          js_script: {
            type: 'string',
            description: 'The javascript code to execute on the page',
          },
        },
        required: ['url', 'js_script'],
      },
    },
  • Handler logic for 'scrape_webpage_js': destructures arguments, calls makeRequest to FetchSERP API endpoint '/api/v1/scrape_js' with POST method, passing URL and JS script in body.
    case 'scrape_webpage_js':
      const { url, js_script, ...jsParams } = args;
      return await this.makeRequest('/api/v1/scrape_js', 'POST', { url, ...jsParams }, { url, js_script }, token);
  • Helper method 'makeRequest' that performs authenticated HTTP requests to the FetchSERP API, used by all tools including scrape_webpage_js.
    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 the full burden. It mentions 'custom JS' execution but lacks critical behavioral details: whether it runs in a headless browser, handles dynamic content, respects robots.txt, has rate limits, requires authentication, or what the output format is. For a scraping tool 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 extremely concise with a single, front-loaded sentence that directly states the tool's purpose. Every word earns its place, making it efficient and easy to parse without unnecessary elaboration.

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 web scraping with JavaScript execution, no annotations, and no output schema, the description is incomplete. It fails to address key aspects like execution environment, error handling, performance constraints, or return values, leaving significant gaps for an AI agent to understand proper usage.

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%, with clear descriptions for both parameters ('url' and 'js_script'). The description adds minimal value beyond the schema, only implying that 'js_script' is custom JavaScript code, which is already covered. 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.

Purpose4/5

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

The description clearly states the action ('scrape') and resource ('web page'), and specifies the distinctive feature ('with custom JS'). However, it doesn't explicitly differentiate from its sibling 'scrape_webpage' or 'scrape_webpage_js_proxy', which likely offer similar functionality without custom JavaScript execution.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as requiring JavaScript knowledge, or compare it to siblings like 'scrape_webpage' (likely for basic scraping) or 'scrape_webpage_js_proxy' (possibly for proxied execution).

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