Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_bulk_backlinks

Analyze backlink counts for up to 1000 domains, subdomains, or pages to assess link-building effectiveness and competitive research.

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 handle method executes the tool logic: sends a POST request to DataForSEO's /v3/backlinks/bulk_backlinks/live endpoint with the targets array, validates and formats the response, or formats errors.
    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);
      }
    }
  • Defines the input schema using Zod: an object with 'targets' property, which is a required array of strings representing domains, subdomains, or full URLs (up to 1000).
      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 instantiates BacklinksBulkBacklinksTool (line 33) along with other tools and registers them into a record keyed by tool name, providing description, params, and handler wrapper.
    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),
        },
      }), {});
    }
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. It discloses that the tool provides counts of 'all live backlinks' including various attributes (e.g., nofollow) and is based on the 'latest check,' which adds useful context about data freshness and inclusivity. However, it lacks details on permissions, rate limits, or error handling, which are important for a bulk operation 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 sized with two sentences: the first states the core purpose and scope, and the second clarifies domain handling. It is front-loaded with key information and avoids unnecessary details, though the second sentence could be integrated more seamlessly for slightly better flow.

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 counts), no annotations, and no output schema, the description is somewhat complete but has gaps. It explains what the tool does and data specifics, but lacks information on output format (e.g., structure of returned counts), error cases, or performance considerations, which are important for effective use by an agent.

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 the 'targets' parameter with examples and constraints. The description adds minimal value by mentioning 'targets array' and clarifying domain/subdomain/page distinctions, but does not provide additional semantics beyond what the schema already covers, meeting the baseline for high 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 from sibling tools like 'backlinks_backlinks' or 'backlinks_summary', which likely serve similar purposes with different scopes or details.

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' from the 'latest check' and clarifies domain vs. subdomain handling. However, it does not explicitly state when to use this tool versus alternatives (e.g., 'backlinks_backlinks' for detailed backlink lists or 'backlinks_summary' for aggregated metrics), leaving the agent to infer based on the 'bulk' nature and focus on counts.

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