Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_bulk_new_lost_backlinks

Analyze new and lost backlinks for multiple domains or pages to monitor link profile changes and identify opportunities or risks in SEO performance.

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" ]
date_fromNostarting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks; the backlinks that appeared in our index after the specified date will be considered as new; the backlinks that weren’t found after the specified date, but were present before, will be considered as lost; default value: today’s date -(minus) one month; e.g. if today is 2021-10-13, default date_from will be 2021-09-13. minimum value equals today’s date -(minus) one year; e.g. if today is 2021-10-13, minimum date_from will be 2020-10-13. date format: "yyyy-mm-dd" example: "2021-01-01"

Implementation Reference

  • The async handle method implements the core logic of the tool by sending a POST request to the DataForSEO Backlinks Bulk New Lost Backlinks endpoint with the provided targets.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/bulk_new_lost_backlinks/live', 'POST', [{
          targets: params.targets
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Defines the Zod schema for input parameters: required 'targets' array of strings and optional 'date_from' string.
      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"
    ]`),
    date_from: z.string().optional().describe(`starting date of the time range
    optional field
    this field indicates the date which will be used as a threshold for new and lost backlinks;
    the backlinks that appeared in our index after the specified date will be considered as new;
    the backlinks that weren’t found after the specified date, but were present before, will be considered as lost;
    default value: today’s date -(minus) one month;
    e.g. if today is 2021-10-13, default date_from will be 2021-09-13.
    minimum value equals today’s date -(minus) one year;
    e.g. if today is 2021-10-13, minimum date_from will be 2020-10-13.
    
    date format: "yyyy-mm-dd"
    example:
    "2021-01-01"`)
        };
      }
  • Instantiates the BacklinksBulkNewLostBacklinksTool within the BacklinksApiModule's getTools method, registering it for use.
    new BacklinksBulkNewLostBacklinksTool(this.dataForSEOClient),
  • Imports the tool class necessary for its registration in the module.
    import { BacklinksBulkNewLostBacklinksTool } from './tools/backlinks-bulk-new-lost-backlinks.tool.js';
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden of behavioral disclosure. It adds some context: it specifies that results are based on 'all live referring domains' and 'latest check', and clarifies domain vs. subdomain handling. However, it lacks details on permissions, rate limits, error handling, or response format, leaving gaps for a tool with potential data sensitivity.

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 first sentence stating the core purpose. The second sentence adds important behavioral context, and the note clarifies domain handling. 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 no annotations and no output schema, the description provides basic purpose and some behavioral context but is incomplete. It lacks details on output format, error cases, or advanced usage scenarios, which are important for a tool with two parameters and no structured output documentation. It is adequate but has clear gaps.

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 already documents both parameters thoroughly. The description adds minimal value beyond the schema: it mentions 'targets array' and implies date-based filtering for 'new and lost backlinks', but does not provide additional syntax or format details. This meets the baseline 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 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_bulk_referring_domains' or 'backlinks_bulk_new_lost_referring_domains', which likely offer similar backlink data.

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 by detailing what the tool returns (e.g., based on 'latest check' and handling of domains vs. subdomains), but does not explicitly state when to use this tool versus alternatives. It mentions that results are for 'new and lost backlinks' via the 'date_from' parameter context, but lacks direct guidance on scenarios or prerequisites for choosing this over other backlink tools.

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