Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_bulk_referring_domains

Get referring domain counts for multiple websites or pages to analyze backlink profiles and assess domain authority across your target list.

Instructions

This endpoint will provide you with the number of referring domains pointing to domains, subdomains, and pages specified in the targets array. The returned numbers are based on all live referring domains, that is, total number of domains pointing to the target with any type of backlinks (e.g., nofollow, noreferrer, ugc, sponsored etc) that were found during the latest check. Note that if you indicate a domain as a target, you will get result for the root domain (domain with all of its subdomains), e.g. dataforseo.com and app.dataforseo.com

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetsYesdomains, subdomains or webpages to get rank for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: "targets": [ "forbes.com", "cnn.com", "bbc.com", "yelp.com", "https://www.apple.com/iphone/", "https://ahrefs.com/blog/", "ibm.com", "https://variety.com/", "https://stackoverflow.com/", "www.trustpilot.com" ]

Implementation Reference

  • The handle method implements the core logic of the 'backlinks_bulk_referring_domains' tool by making a POST request to the DataForSEO API endpoint '/v3/backlinks/bulk_referring_domains/live' with the targets parameter.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/bulk_referring_domains/live', 'POST', [{
          targets: params.targets
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Defines the input schema using Zod for the 'targets' parameter, an array of up to 1000 domains, subdomains, or full URLs.
      getParams(): z.ZodRawShape {
        return {
          targets: z.array(z.string()).describe(`domains, subdomains or webpages to get rank for
    required field
    you can set up to 1000 domains, subdomains or webpages
    the domain or subdomain should be specified without https:// and www.
    the page should be specified with absolute URL (including http:// or https://)
    example:
    "targets": [
    "forbes.com",
    "cnn.com",
    "bbc.com",
    "yelp.com",
    "https://www.apple.com/iphone/",
    "https://ahrefs.com/blog/",
    "ibm.com",
    "https://variety.com/",
    "https://stackoverflow.com/",
    "www.trustpilot.com"
    ]`)
        };
      }
  • Registers the BacklinksBulkReferringDomainsTool (instantiated at line 39 relative to this block) along with other tools into a record keyed by tool name, exposing description, params schema, and handler function.
    getTools(): Record<string, ToolDefinition> {
      const tools = [
        new BacklinksTool(this.dataForSEOClient),
        new BacklinksAnchorTool(this.dataForSEOClient),
        new BacklinksBulkBacklinksTool(this.dataForSEOClient),
        new BacklinksBulkNewLostReferringDomainsTool(this.dataForSEOClient),
        new BacklinksBulkNewLostBacklinksTool(this.dataForSEOClient),
        new BacklinksBulkRanksTool(this.dataForSEOClient),
        new BacklinksBulkReferringDomainsTool(this.dataForSEOClient),
        new BacklinksBulkSpamScoreTool(this.dataForSEOClient),
        new BacklinksCompetitorsTool(this.dataForSEOClient),
        new BacklinksDomainIntersectionTool(this.dataForSEOClient),
        new BacklinksDomainPagesSummaryTool(this.dataForSEOClient),
        new BacklinksDomainPagesTool(this.dataForSEOClient),
        new BacklinksPageIntersectionTool(this.dataForSEOClient),
        new BacklinksReferringDomainsTool(this.dataForSEOClient),
        new BacklinksReferringNetworksTool(this.dataForSEOClient),
        new BacklinksSummaryTool(this.dataForSEOClient),
        new BacklinksTimeseriesNewLostSummaryTool(this.dataForSEOClient),
        new BacklinksTimeseriesSummaryTool(this.dataForSEOClient),
        new BacklinksBulkPagesSummaryTool(this.dataForSEOClient),
        new BacklinksFiltersTool(this.dataForSEOClient)
        // Add more tools here
      ];
    
      return tools.reduce((acc, tool) => ({
        ...acc,
        [tool.getName()]: {
          description: tool.getDescription(),
          params: tool.getParams(),
          handler: (params: any) => tool.handle(params),
        },
      }), {});
    }
  • Imports the BacklinksBulkReferringDomainsTool class required for instantiation and registration.
    import { BacklinksBulkReferringDomainsTool } from './tools/backlinks-bulk-referring-domains.tool.js';
  • Returns the exact tool name 'backlinks_bulk_referring_domains' used for registration and invocation.
    getName(): string {
      return 'backlinks_bulk_referring_domains';
    }
Behavior3/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 adds useful context: it specifies that results are based on 'all live referring domains' from the 'latest check' and includes all backlink types (e.g., nofollow). However, it does not cover critical aspects like rate limits, authentication needs, error handling, or response format, leaving gaps for a tool with potential performance implications.

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 appropriately sized and front-loaded, with the core purpose stated in the first sentence. The second sentence clarifies scope and data recency, and the third explains domain vs. subdomain handling. Each sentence adds value, though the structure could be slightly more streamlined (e.g., merging the second and third points).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (bulk analysis with up to 1000 targets), no annotations, and no output schema, the description is moderately complete. It covers the purpose, data source, and target handling, but lacks details on output format (e.g., JSON structure), pagination, error cases, or performance considerations, which are important for effective use.

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 the 'targets' parameter fully documented in the schema (including examples, formatting rules, and limits). The description adds minimal value beyond the schema, only reiterating that targets include 'domains, subdomains, and pages.' This meets the baseline score of 3, as the schema does the heavy lifting.

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

Purpose5/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 the number of referring domains pointing to domains, subdomains, and pages specified in the targets array.' It specifies the verb ('provide'), resource ('number of referring domains'), and scope ('domains, subdomains, and pages'), distinguishing it from siblings like 'backlinks_backlinks' or 'backlinks_summary' by focusing on bulk referring domain counts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for bulk referring domain analysis but does not explicitly state when to use this tool versus alternatives like 'backlinks_referring_domains' (likely for single targets) or 'backlinks_bulk_new_lost_referring_domains' (for tracking changes). It provides some context about target types and domain vs. subdomain handling, but lacks clear guidance on tool selection among siblings.

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