Skip to main content
Glama
fetchSERP

FetchSERP MCP Server

Official
by fetchSERP

get_backlinks

Analyze and retrieve backlinks for a specified domain using selected search engine, country, and page count to enhance SEO strategy and competitive insights.

Instructions

Get backlinks for a given domain

Input Schema

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

Implementation Reference

  • The handler logic for the 'get_backlinks' tool, which forwards the request parameters to the FetchSERP API's backlinks endpoint via the makeRequest helper.
    case 'get_backlinks':
      return await this.makeRequest('/api/v1/backlinks', 'GET', args, null, token);
  • Input schema defining parameters for the get_backlinks tool: domain (required), search_engine, country, pages_number.
    inputSchema: {
      type: 'object',
      properties: {
        domain: {
          type: 'string',
          description: 'The domain to search for backlinks',
        },
        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: 15',
          default: 15,
          minimum: 1,
          maximum: 30,
        },
      },
      required: ['domain'],
    },
  • index.js:40-70 (registration)
    Registration of the 'get_backlinks' tool in the ListTools response, including name, description, and schema.
    {
      name: 'get_backlinks',
      description: 'Get backlinks for a given domain',
      inputSchema: {
        type: 'object',
        properties: {
          domain: {
            type: 'string',
            description: 'The domain to search for backlinks',
          },
          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: 15',
            default: 15,
            minimum: 1,
            maximum: 30,
          },
        },
        required: ['domain'],
      },
    },
  • Helper function makeRequest used by get_backlinks (and other tools) 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 the full burden of behavioral disclosure. It states the tool 'gets' backlinks, implying a read-only operation, but doesn't mention any behavioral traits such as rate limits, authentication needs, data freshness, or what the output format looks like (e.g., list of URLs with metadata). This leaves significant gaps for an agent to understand how the tool 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 a single, efficient sentence that directly states the tool's purpose without any fluff. It's front-loaded and wastes no words, making it easy for an agent to parse quickly.

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 incomplete for a tool with 4 parameters and potential complexity (e.g., backlink analysis). It doesn't cover behavioral aspects, output format, or usage context, which are critical for an agent to invoke this tool effectively in a server with many sibling tools.

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 all parameters well-documented in the schema (e.g., domain, country, pages_number, search_engine). The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or usage nuances. Baseline 3 is appropriate since 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 ('Get') and resource ('backlinks for a given domain'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_domain_info' or 'scrape_domain', which might also involve domain analysis, but the specific focus on backlinks is clear.

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_domain_info' or 'scrape_domain' that might overlap in domain-related queries, there's no indication of context, prerequisites, or exclusions to help an agent choose appropriately.

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