Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_referring_networks

Analyze referring networks and IP addresses linking to a target domain or webpage to identify backlink patterns and potential link farms.

Instructions

This endpoint will provide you with a detailed overview of referring domains pointing to the target you specify

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesdomain, subdomain or webpage to get backlinks for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)
network_address_typeNoindicates the type of network to get data for optional field possible values: ip, subnet default value: ipip
limitNothe maximum number of returned networks
offsetNooffset in the results array of returned networks optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages
filtersNoarray of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, <>, in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: ["referring_pages",">","1"] [["referring_pages",">","2"], "and", ["backlinks",">","10"]] [["first_seen",">","2017-10-23 11:31:45 +00:00"], "and", [["network_address","like","194.1.%"],"or",["referring_ips",">","10"]]]
order_byNoresults sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: ["backlinks,desc"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ["backlinks,desc","rank,asc"]

Implementation Reference

  • The handle method implements the core tool logic: formats input parameters, makes a POST request to DataForSEO's '/v3/backlinks/referring_networks/live' endpoint, validates/formats the response or handles errors.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/referring_networks/live', 'POST', [{
          target: params.target,
          limit: params.limit,
          offset: params.offset,
          filters: this.formatFilters(params.filters),
          order_by: this.formatOrderBy(params.order_by),
          network_address_type: params.network_address_type
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Defines the Zod schema for input parameters: target (required), network_address_type, limit, offset, filters, order_by with detailed descriptions and constraints.
      getParams(): z.ZodRawShape {
        return {
          target: z.string().describe(`domain, subdomain or webpage to get backlinks for
            required field
    a domain or a subdomain should be specified without https:// and www.
    a page should be specified with absolute URL (including http:// or https://)`),
          network_address_type: z.string().optional().default('ip').describe(`indicates the type of network to get data for
    optional field
    possible values: ip, subnet
    default value: ip`),
          limit: z.number().min(1).max(1000).default(10).optional().describe("the maximum number of returned networks"),
          offset: z.number().min(0).optional().describe(
            `offset in the results array of returned networks
    optional field
    default value: 0
    if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages`
          ),
          filters: z.array(
            z.union([
              z.array(z.union([z.string(), z.number(), z.boolean()])).length(3),
              z.enum(["and", "or"])
            ])
          ).max(8).optional().describe(
            `array of results filtering parameters
    optional field
    you can add several filters at once (8 filters maximum)
    you should set a logical operator and, or between the conditions
    the following operators are supported:
    regex, not_regex, =, <>, in, not_in, like, not_like, ilike, not_ilike, match, not_match
    you can use the % operator with like and not_like to match any string of zero or more characters
    example:
    ["referring_pages",">","1"]
    [["referring_pages",">","2"],
    "and",
    ["backlinks",">","10"]]
    
    [["first_seen",">","2017-10-23 11:31:45 +00:00"],
    "and",
    [["network_address","like","194.1.%"],"or",["referring_ips",">","10"]]]`
          ),
          order_by: z.array(z.string()).optional().describe(
            `results sorting rules
    optional field
    you can use the same values as in the filters array to sort the results
    possible sorting types:
    asc – results will be sorted in the ascending order
    desc – results will be sorted in the descending order
    you should use a comma to set up a sorting type
    example:
    ["backlinks,desc"]
    note that you can set no more than three sorting rules in a single request
    you should use a comma to separate several sorting rules
    example:
    ["backlinks,desc","rank,asc"]`
          ),
        };
      }
  • Instantiates BacklinksReferringNetworksTool in the getTools() method of BacklinksApiModule. The tool is then registered in the returned object using its getName() as key, with description, params, and wrapped handle function.
    new BacklinksReferringNetworksTool(this.dataForSEOClient),
  • Maps the tool name 'backlinks_referring_networks' to the API response path 'referring_networks' in TOOL_TO_FILTER_MAP, used by BacklinksFiltersTool to provide filter information for this endpoint.
    'backlinks_referring_networks': 'referring_networks',
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool as providing 'a detailed overview' but doesn't specify what that overview contains, whether it's paginated (though the schema suggests it is via limit/offset), rate limits, authentication requirements, or potential costs/limitations. For a tool with 6 parameters and complex filtering capabilities, this minimal description leaves significant behavioral aspects undocumented.

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 - a single sentence that directly states the tool's purpose. There's no wasted language, repetition, or unnecessary elaboration. It's front-loaded with the core functionality and doesn't bury important information. For a tool with comprehensive schema documentation, this brevity is appropriate.

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 complexity (6 parameters including complex filtering arrays), lack of annotations, and no output schema, the single-sentence description is inadequate. The schema handles parameter documentation well, but the description fails to provide necessary context about what 'referring networks' means versus 'referring domains', what the output structure looks like, or behavioral considerations. For a tool with this level of complexity, more contextual information is needed.

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 schema description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description adds no additional parameter semantics beyond what's already in the schema descriptions. It mentions 'the target you specify' which aligns with the 'target' parameter, but provides no extra context about parameter usage, relationships, or examples beyond what the schema already contains.

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: 'provide you with a detailed overview of referring domains pointing to the target you specify.' It specifies the verb ('provide'), resource ('detailed overview of referring domains'), and target scope ('pointing to the target you specify'). However, it doesn't explicitly differentiate from sibling tools like 'backlinks_referring_domains' or 'backlinks_backlinks', which likely provide similar backlink data but at different granularity levels.

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 multiple backlinks-related sibling tools (e.g., 'backlinks_referring_domains', 'backlinks_backlinks', 'backlinks_summary'), there's no indication of what makes this 'referring networks' tool distinct or when it should be preferred over other backlink analysis tools. The description only states what the tool does, not when to use it.

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

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/ravinwebsurgeon/seo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server