Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_referring_domains

Analyze referring domains pointing to any website or webpage to understand backlink sources and domain authority for SEO strategy development.

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: ["meta.internal_links_count",">","1"] [["meta.external_links_count",">","2"], "and", ["backlinks",">","10"]] [["first_visited",">","2017-10-23 11:31:45 +00:00"], "and", [["title","like","%seo%"],"or",["referring_domains",">","10"]]]
limitNothe maximum number of returned pages
offsetNooffset in the results array of returned pages optional field default value: 0 if you specify the 10 value, the first ten pages 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: ["page_summary.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: ["page_summary.backlinks,desc","page_summary.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 main handler function that implements the tool logic: makes a POST request to DataForSEO's /v3/backlinks/referring_domains/live endpoint with parameters, formats filters and order_by, validates response, or handles errors.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/referring_domains/live', 'POST', [{
          target: params.target,
          limit: params.limit,
          offset: params.offset,
          filters: this.formatFilters(params.filters),
          order_by: this.formatOrderBy(params.order_by),
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Defines the input schema using Zod for parameters: target (required), limit, offset, filters, order_by.
      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://)`),
          limit: z.number().min(1).max(1000).default(10).optional().describe("the maximum number of returned pages"),
          offset: z.number().min(0).optional().describe(
            `offset in the results array of returned pages
    optional field
    default value: 0
    if you specify the 10 value, the first ten pages 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:
    ["meta.internal_links_count",">","1"]
    [["meta.external_links_count",">","2"],
    "and",
    ["backlinks",">","10"]]
    
    [["first_visited",">","2017-10-23 11:31:45 +00:00"],
    "and",
    [["title","like","%seo%"],"or",["referring_domains",">","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:
    ["page_summary.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:
    ["page_summary.backlinks,desc","page_summary.rank,asc"]`
          ),
        };
      }
  • Registers the BacklinksReferringDomainsTool by instantiating it in the tools array within the getTools() method, which maps tool names to their definitions including handlers.
    new BacklinksReferringDomainsTool(this.dataForSEOClient),
  • Imports the BacklinksReferringDomainsTool class necessary for its registration.
    import { BacklinksReferringDomainsTool } from './tools/backlinks-referring-domains.tool.js';
  • Defines the tool name 'backlinks_referring_domains' used for registration and identification.
    getName(): string {
      return 'backlinks_referring_domains';
    }
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 mentions providing a 'detailed overview' but doesn't specify what that includes (e.g., domain metrics, link counts, timestamps), whether results are paginated (implied by limit/offset but not stated), or any rate limits/authentication requirements. For a data retrieval tool with no annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that directly states the tool's purpose. There's no wasted verbiage, and it's appropriately front-loaded with the core functionality. However, it could be slightly more structured by explicitly mentioning key capabilities like filtering or pagination.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the 'detailed overview' includes (output format), how results are structured, or any behavioral constraints. Given the complexity implied by the filtering/sorting parameters and lack of structured metadata, the description should provide more context about the tool's operation and results.

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 fully documents all 5 parameters. The description doesn't add any meaningful parameter semantics beyond what's in the schema—it mentions 'target you specify' which is covered by the schema's target parameter description. Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 includes a specific verb ('provide') and resource ('referring domains'), but doesn't explicitly differentiate from sibling tools like 'backlinks_referring_networks' or 'backlinks_summary' which might offer similar data.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools in the 'backlinks_' category (e.g., 'backlinks_backlinks', 'backlinks_summary'), the description lacks any context about what makes this tool unique or when it should be preferred over others for analyzing referring domains.

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