Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_referring_domains

Analyze referring domains pointing to a target domain, subdomain, or webpage to assess backlink profiles and SEO authority.

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://)
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
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"]]]
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"]

Implementation Reference

  • The main handler function that executes the tool logic by making a POST request to the DataForSEO Backlinks API '/v3/backlinks/referring_domains/live' endpoint with the provided parameters, formats filters and order_by, and handles response or 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 Zod schema for input parameters: target (required string), limit, offset, filters (complex array), 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: 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:
    ["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 tool in the BacklinksApiModule's getTools() method by including its instance in the tools array and reducing to a map with name, description, params, and handler wrapper.
    return tools.reduce((acc, tool) => ({
      ...acc,
      [tool.getName()]: {
        description: tool.getDescription(),
        params: tool.getParams(),
        handler: (params: any) => tool.handle(params),
      },
    }), {});
  • Instantiates the BacklinksReferringDomainsTool with the DataForSEO client for registration in the module.
    new BacklinksReferringDomainsTool(this.dataForSEOClient),
  • Maps the tool name to its corresponding filter path 'referring_domains' for use in the filters tool.
    private static readonly TOOL_TO_FILTER_MAP: { [key: string]: string } = {
      'backlinks_content_duplicates': 'content_duplicates',
      'backlinks_backlinks': 'backlinks',
      'backlinks_domain_pages': 'domain_pages',
      'backlinks_anchors': 'anchors',
      'backlinks_referring_domains': 'referring_domains',
      'backlinks_domain_intersection': 'domain_intersection',
      'backlinks_page_intersection': 'page_intersection',
      'backlinks_referring_networks': 'referring_networks',
      'backlinks_domain_pages_summary': 'domain_pages_summary',
      'backlinks_competitors': 'competitors'
    };
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 provides a 'detailed overview,' implying a read-only operation, but doesn't clarify if it's safe, if it has rate limits, authentication needs, or what the output format entails (e.g., pagination, data structure). For a tool with complex parameters like filters and order_by, this lack of behavioral context is a significant gap.

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 front-loads the core purpose without unnecessary details. It avoids redundancy and wastes no words, making it easy to parse quickly. This is ideal for conciseness, as every part of the sentence contributes directly to understanding the tool's function.

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 (5 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain the output format, behavioral traits like safety or limits, or how to interpret results. While the schema covers inputs well, the description fails to provide necessary context for effective use, especially for a data-fetching tool with filtering and sorting capabilities.

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%, meaning the input schema fully documents all 5 parameters with detailed descriptions and examples. The description adds no additional parameter semantics beyond implying the 'target' is for backlinks, which is already clear from the schema. Thus, it meets the baseline of 3, as the schema does the heavy lifting without extra value from the description.

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 uses specific verbs ('provide,' 'pointing') and identifies the resource ('referring domains'), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'backlinks_backlinks' or 'backlinks_referring_networks,' which likely offer related backlink data, so it misses full sibling distinction.

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. It doesn't mention sibling tools or contexts where this is preferred, such as for domain-level vs. page-level analysis. Without any usage context, the agent must infer based on the name alone, which is insufficient for optimal tool selection.

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