Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_bulk_backlinks

Get total backlink counts for up to 1000 domains, subdomains, or webpages. Analyze referring links with all attributes including nofollow, noreferrer, ugc, and sponsored tags from live backlink data.

Instructions

This endpoint will provide you with the number of backlinks pointing to domains, subdomains, and pages specified in the targets array. The returned numbers correspond to all live backlinks, that is, total number of referring links with all attributes (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 results 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 core handler function that performs the API request to DataForSEO's /v3/backlinks/bulk_backlinks/live endpoint using the provided targets array.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/bulk_backlinks/live', 'POST', [{
          targets: params.targets
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Zod schema defining the input parameters: 'targets' as an array of strings (domains, subdomains, or full URLs). Includes detailed description and example.
        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"
    ]`)
        };
      }
  • Instantiation of the BacklinksBulkBacklinksTool within the BacklinksApiModule's getTools() method, which registers it by name via tool.getName().
    new BacklinksBulkBacklinksTool(this.dataForSEOClient),
  • Import of the BacklinksBulkBacklinksTool class necessary for its registration in the module.
    import { BacklinksBulkBacklinksTool } from './tools/backlinks-bulk-backlinks.tool.js';
  • The getName() method that returns the exact tool name 'backlinks_bulk_backlinks' used for registration.
    getName(): string {
      return 'backlinks_bulk_backlinks';
    }
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 about what the tool returns ('number of backlinks', 'all live backlinks', 'total number of referring links with all attributes') and clarifies domain-level results. However, it lacks details on rate limits, authentication needs, error handling, or response format, which are critical for a tool with no output schema.

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 with two sentences that front-load the core functionality and follow with a clarifying note. Each sentence adds value: the first defines the tool's purpose and scope, and the second explains domain-level behavior. There is no wasted text, though it could be slightly more structured for readability.

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 moderate complexity (bulk backlink counting), no annotations, and no output schema, the description is incomplete. It covers the basic purpose and some behavioral context but lacks details on output structure, pagination, error cases, or performance considerations. This leaves gaps for an agent to invoke the tool effectively without additional context.

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 constraints. The description adds minimal semantic value beyond the schema, only reiterating that targets include 'domains, subdomains, and pages' and clarifying domain vs. subdomain results. This meets the baseline score of 3 for high schema coverage.

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 backlinks pointing to domains, subdomains, and pages specified in the targets array.' It specifies the verb ('provide'), resource ('number of backlinks'), and scope ('domains, subdomains, and pages'), but does not explicitly differentiate it from sibling tools like 'backlinks_backlinks' or 'backlinks_summary', which likely have overlapping functionality.

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 context by specifying that it returns 'all live backlinks... found during the latest check' and clarifies domain vs. subdomain handling. However, it does not explicitly state when to use this tool versus alternatives like 'backlinks_backlinks' or 'backlinks_bulk_referring_domains', nor does it provide exclusions or prerequisites, leaving the agent to infer based on the 'bulk' nature and target array.

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