Skip to main content
Glama
fetchSERP

FetchSERP MCP Server

Official
by fetchSERP

get_serp_html

Extract HTML content from search engine results pages (SERPs) for specific queries, search engines, and countries using the FetchSERP MCP Server.

Instructions

Get search engine results with HTML content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoThe country to search from. Default: usus
pages_numberNoThe number of pages to search (1-30). Default: 1
queryYesThe query to search
search_engineNoThe search engine to use (google, bing, yahoo, duckduckgo). Default: googlegoogle

Implementation Reference

  • Handler implementation for the 'get_serp_html' tool. It calls the shared makeRequest method with the specific API endpoint '/api/v1/serp_html'.
    case 'get_serp_html':
      return await this.makeRequest('/api/v1/serp_html', 'GET', args, null, token);
  • Input schema defining parameters for the 'get_serp_html' tool: query (required), search_engine, country, pages_number.
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'The query to search',
        },
        search_engine: {
          type: 'string',
          description: 'The search engine to use (google, bing, yahoo, duckduckgo). Default: google',
          default: 'google',
        },
        country: {
          type: 'string',
          description: 'The country to search from. Default: us',
          default: 'us',
        },
        pages_number: {
          type: 'integer',
          description: 'The number of pages to search (1-30). Default: 1',
          default: 1,
          minimum: 1,
          maximum: 30,
        },
      },
      required: ['query'],
    },
  • index.js:355-385 (registration)
    Registration of the 'get_serp_html' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'get_serp_html',
      description: 'Get search engine results with HTML content',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'The query to search',
          },
          search_engine: {
            type: 'string',
            description: 'The search engine to use (google, bing, yahoo, duckduckgo). Default: google',
            default: 'google',
          },
          country: {
            type: 'string',
            description: 'The country to search from. Default: us',
            default: 'us',
          },
          pages_number: {
            type: 'integer',
            description: 'The number of pages to search (1-30). Default: 1',
            default: 1,
            minimum: 1,
            maximum: 30,
          },
        },
        required: ['query'],
      },
    },
  • Shared helper method that performs authenticated HTTP requests to the FetchSERP API using node-fetch, used by all tools including get_serp_html.
    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. It states the tool retrieves search results with HTML content but doesn't mention rate limits, authentication needs, pagination behavior, error handling, or what 'HTML content' entails (e.g., raw HTML, structured data). For a tool with no annotation coverage, this leaves significant gaps in understanding its operational behavior.

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, efficient sentence: 'Get search engine results with HTML content'. It's front-loaded with the core purpose, has zero wasted words, and is appropriately sized for the tool's complexity. Every part of the sentence contributes essential 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 the tool's moderate complexity (4 parameters, no output schema, no annotations), the description is incomplete. It lacks behavioral details (e.g., rate limits, error handling), usage guidelines compared to siblings, and clarification on the output format. Without annotations or an output schema, the description should provide more context to help an agent use the 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?

The input schema has 100% description coverage, with clear documentation for all four parameters (query, country, pages_number, search_engine), including defaults and constraints. The description adds no additional parameter semantics beyond what's in the schema, such as explaining how parameters interact or providing usage examples. With high schema coverage, the baseline score of 3 is appropriate.

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: 'Get search engine results with HTML content'. It specifies the verb ('Get'), resource ('search engine results'), and output format ('HTML content'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'get_serp_results' or 'get_serp_text', which likely provide different output formats or levels of detail.

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 sibling tools like 'get_serp_results' or 'get_serp_text', nor does it specify scenarios where HTML content is preferred over other formats. There's no context about prerequisites, limitations, or typical use cases.

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