Skip to main content
Glama
fetchSERP

FetchSERP MCP Server

Official
by fetchSERP

scrape_webpage_js_proxy

Scrape web pages using JavaScript execution and proxy integration for dynamic content extraction, ideal for SEO analysis and data collection.

Instructions

Scrape a web page with JS and proxy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesThe country to use for the proxy
js_scriptYesThe javascript code to execute on the page
urlYesThe url to scrape

Implementation Reference

  • The handler logic for the 'scrape_webpage_js_proxy' tool. It destructures the input arguments (renaming url and js_script for the request body), constructs query parameters from remaining args, and makes a POST request to the '/api/v1/scrape_js_with_proxy' endpoint using the shared makeRequest method.
    case 'scrape_webpage_js_proxy':
      const { url: proxyUrl, country, js_script: proxyScript, ...proxyParams } = args;
      return await this.makeRequest('/api/v1/scrape_js_with_proxy', 'POST', { url: proxyUrl, country, ...proxyParams }, { url: proxyUrl, js_script: proxyScript }, token);
  • Input schema definition for the 'scrape_webpage_js_proxy' tool, specifying properties for url, country, js_script, and required fields.
    inputSchema: {
      type: 'object',
      properties: {
        url: {
          type: 'string',
          description: 'The url to scrape',
        },
        country: {
          type: 'string',
          description: 'The country to use for the proxy',
        },
        js_script: {
          type: 'string',
          description: 'The javascript code to execute on the page',
        },
      },
      required: ['url', 'country', 'js_script'],
  • index.js:302-323 (registration)
    Registration of the 'scrape_webpage_js_proxy' tool in the listTools response, including name, description, and input schema.
    {
      name: 'scrape_webpage_js_proxy',
      description: 'Scrape a web page with JS and proxy',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'The url to scrape',
          },
          country: {
            type: 'string',
            description: 'The country to use for the proxy',
          },
          js_script: {
            type: 'string',
            description: 'The javascript code to execute on the page',
          },
        },
        required: ['url', 'country', 'js_script'],
      },
    },
  • Shared helper method used by all tools, including scrape_webpage_js_proxy, to make 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 the full burden of behavioral disclosure. While it mentions JS execution and proxy usage, it doesn't describe important behavioral aspects like rate limits, authentication requirements, error handling, what gets returned (HTML? structured data?), or performance characteristics. For a scraping tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 at just 6 words, with zero wasted language. Every word contributes meaning: 'scrape' (action), 'web page' (resource), 'with JS' (capability), 'and proxy' (additional capability). It's perfectly front-loaded with the core functionality.

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?

For a scraping tool with 3 required parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, how JavaScript execution works, proxy limitations, error conditions, or performance expectations. Given the complexity of web scraping with JS and proxies, more context is needed for the agent to use this tool effectively.

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 all parameters are documented in the schema. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions. It mentions 'proxy' which relates to the 'country' parameter, but doesn't provide additional context about proxy behavior, JS execution constraints, or URL requirements beyond the schema's basic descriptions.

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 two key capabilities: using JavaScript execution and proxy support. However, it doesn't differentiate from sibling tools like 'scrape_webpage' or 'scrape_webpage_js', leaving some ambiguity about when this specific tool should be chosen over those alternatives.

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?

No guidance is provided about when to use this tool versus alternatives. With sibling tools like 'scrape_webpage' and 'scrape_webpage_js' available, the description doesn't explain what makes this proxy version different or when it's preferred over non-proxy scraping tools. No context about use cases or exclusions is 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

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