Skip to main content
Glama
fetchSERP

FetchSERP MCP Server

Official
by fetchSERP

get_domain_ranking

Retrieve domain ranking for a specific keyword across search engines, providing insights into SEO performance by analyzing SERP data for targeted keywords and domains.

Instructions

Get domain ranking for a given keyword

Input Schema

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

Implementation Reference

  • Handler case for the 'get_domain_ranking' tool. It calls the shared makeRequest method with the specific API endpoint '/api/v1/ranking' to execute the tool logic.
    case 'get_domain_ranking':
      return await this.makeRequest('/api/v1/ranking', 'GET', args, null, token);
  • Input schema validation for the get_domain_ranking tool, defining parameters: keyword (required), domain (required), search_engine, country, pages_number.
    inputSchema: {
      type: 'object',
      properties: {
        keyword: {
          type: 'string',
          description: 'The keyword to search',
        },
        domain: {
          type: 'string',
          description: 'The domain 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: 10',
          default: 10,
          minimum: 1,
          maximum: 30,
        },
      },
      required: ['keyword', 'domain'],
    },
  • index.js:215-249 (registration)
    Registration of the 'get_domain_ranking' tool in the listTools handler response, providing name, description, and input schema.
    {
      name: 'get_domain_ranking',
      description: 'Get domain ranking for a given keyword',
      inputSchema: {
        type: 'object',
        properties: {
          keyword: {
            type: 'string',
            description: 'The keyword to search',
          },
          domain: {
            type: 'string',
            description: 'The domain 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: 10',
            default: 10,
            minimum: 1,
            maximum: 30,
          },
        },
        required: ['keyword', 'domain'],
      },
    },
  • Shared helper method makeRequest used by the get_domain_ranking handler (and others) 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 'Get domain ranking' but doesn't disclose what ranking means (e.g., SERP position, score), whether this is a read-only operation, potential rate limits, authentication needs, or what the output format looks like. The description is too minimal to provide meaningful behavioral context beyond the basic action.

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 that states the core purpose without unnecessary words. It's appropriately sized for a tool with good schema documentation and gets straight to the point with zero waste.

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 no annotations and no output schema, the description is insufficient for a tool with 5 parameters that performs ranking analysis. It doesn't explain what 'domain ranking' means, what the output contains, or important behavioral aspects like whether this is a read operation, potential costs, or limitations. The description leaves too many contextual gaps for effective tool selection.

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 the schema already documents all 5 parameters thoroughly with descriptions, defaults, and constraints. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter documentation.

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 ('Get') and resource ('domain ranking') with the required input ('for a given keyword'). It distinguishes from most siblings by focusing on ranking rather than content generation, analysis, or scraping. However, it doesn't explicitly differentiate from similar ranking-related tools like 'get_serp_results'.

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. With siblings like 'get_serp_results', 'get_serp_html', and 'get_serp_text' that might provide related search engine data, there's no indication of when this specific ranking-focused tool is preferred or what distinguishes it from those alternatives.

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