Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_bulk_referring_domains

Analyze backlink authority by retrieving the number of referring domains pointing to specified websites, subdomains, or pages for SEO assessment.

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 handler function that executes the tool logic: makes a POST request to DataForSEO API endpoint '/v3/backlinks/bulk_referring_domains/live' with the provided targets and handles response or error.
    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);
      }
    }
  • Zod schema defining the input parameters for the tool, specifically the 'targets' array of domains/subdomains/pages.
      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"
    ]`)
        };
      }
  • The getTools method registers the BacklinksBulkReferringDomainsTool instance along with others, wrapping its handle method as the tool handler in the returned ToolDefinition record.
    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),
        },
      }), {});
    }
  • Import statement for the BacklinksBulkReferringDomainsTool class.
    import { BacklinksBulkReferringDomainsTool } from './tools/backlinks-bulk-referring-domains.tool.js';
  • The getName method returns the exact tool name 'backlinks_bulk_referring_domains' used for registration.
    getName(): string {
      return 'backlinks_bulk_referring_domains';
Behavior3/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. It discloses that results include 'all live referring domains' with 'any type of backlinks' and are from the 'latest check,' adding useful behavioral context. However, it lacks details on rate limits, authentication needs, error handling, or response format (since no output schema exists). The description provides some transparency but misses key operational aspects for a bulk query tool.

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 concise and well-structured. The first sentence clearly states the core functionality, followed by clarifying notes on data recency and domain handling. Each sentence adds value without redundancy, and the text is front-loaded with the main purpose. It could be slightly more efficient by integrating the domain clarification into the initial statement, but overall it avoids waste.

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 querying of referring domains), the description is moderately complete. It covers the purpose and key behavioral notes but lacks output details (no schema provided) and does not address usage relative to siblings. With no annotations and a single well-documented parameter, the description provides a basic understanding but leaves gaps in operational guidance and result interpretation, making it adequate but not fully comprehensive.

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 input schema has 100% description coverage, thoroughly documenting the 'targets' parameter with examples and formatting rules. The description adds minimal semantic value beyond this, only reiterating that targets include 'domains, subdomains, and pages.' Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description does not compensate with additional insights but also does not detract.

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 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 ('targets array'), but does not explicitly differentiate from sibling tools like 'backlinks_referring_domains' or 'backlinks_bulk_new_lost_referring_domains', which appear related. This makes it clear but not fully distinct from alternatives.

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 minimal usage guidance. It notes that results are based on 'all live referring domains' from the 'latest check' and clarifies domain vs. subdomain handling, but does not specify when to use this tool versus sibling tools (e.g., 'backlinks_referring_domains' for single targets or 'backlinks_bulk_new_lost_referring_domains' for changes over time). No explicit alternatives, prerequisites, or exclusions are mentioned, leaving the agent with little contextual direction.

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