Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_referring_networks

Analyze referring networks and domains linking to any website or page to identify backlink sources and assess link-building opportunities for SEO strategy.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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"]]]
limitNothe maximum number of returned networks
network_address_typeNoindicates the type of network to get data for optional field possible values: ip, subnet default value: ipip
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
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"]
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://)

Implementation Reference

  • The handler function that performs the core logic: formats parameters and makes a POST request to the DataForSEO Backlinks Referring Networks live endpoint.
    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);
      }
    }
  • Input schema defined using Zod, specifying parameters like target (required), limit, offset, filters, order_by, and network_address_type.
      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: this.getFilterExpression().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"]`
          ),
        };
      }
  • Tool name definition used for registration.
    getName(): string {
      return 'backlinks_referring_networks';
    }
  • Instantiation of the BacklinksReferringNetworksTool within the BacklinksApiModule's getTools() method for registration into the tool registry.
    new BacklinksReferringNetworksTool(this.dataForSEOClient),
  • Mapping of tool name to API filter path 'referring_networks' used in the filters tool.
    '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 mentions the tool provides a 'detailed overview' but fails to specify output format, pagination behavior, rate limits, authentication needs, or potential side effects. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that efficiently states the tool's function without unnecessary details. It's front-loaded and avoids redundancy, though it could be slightly more informative to improve utility without sacrificing brevity.

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 complexity of 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral traits, output structure, or usage context, making it inadequate for an agent to fully understand how to invoke and interpret results from 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 the input schema already documents all parameters thoroughly. The description adds no additional meaning or context about parameters beyond what the schema provides, such as explaining the 'target' field's relationship to referring networks. Thus, it meets the baseline for high schema coverage without compensating with extra insights.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool provides 'a detailed overview of referring domains pointing to the target you specify,' which clarifies it retrieves referring domain data for a target. However, it's vague about what 'referring domains' means in this context (e.g., networks vs. domains), and it doesn't distinguish this from sibling tools like 'backlinks_referring_domains,' leaving ambiguity in purpose.

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 offers no guidance on when to use this tool versus alternatives, such as 'backlinks_referring_domains' or other backlinks-related siblings. It lacks context on specific use cases, prerequisites, or exclusions, providing only a basic functional statement without comparative or situational advice.

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/cortex8/oyt-dataforseo-mcp-worker'

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