Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

backlinks_bulk_new_lost_referring_domains

Analyze new and lost referring domains for up to 1000 targets to monitor backlink changes over time.

Instructions

This endpoint will provide you with the number of referring domains pointing to the domains, subdomains and pages specified in the targets array. 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 handle method executes the tool logic by making a POST request to DataForSEO's /v3/backlinks/bulk_new_lost_referring_domains/live endpoint with the targets parameter.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/bulk_new_lost_referring_domains/live', 'POST', [{
          targets: params.targets
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Defines the Zod schema for the tool's 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"`)
        };
  • The tool is instantiated and added to the list of tools in BacklinksApiModule's getTools() method, which registers it for use.
    new BacklinksBulkNewLostReferringDomainsTool(this.dataForSEOClient),
  • Import statement for the tool class in the backlinks module.
    import { BacklinksBulkNewLostReferringDomainsTool } from './tools/backlinks-bulk-new-lost-referring-domains.tool.js';
  • Returns the exact tool name used for registration and invocation.
    getName(): string {
      return 'backlinks_bulk_new_lost_referring_domains';
    }
Behavior2/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 of behavioral disclosure. It mentions the tool provides data on 'new and lost' referring domains (implied by the tool name and date_from parameter context), but does not explain what 'new and lost' means operationally, rate limits, authentication needs, or output format. The description is insufficient for a tool that likely involves data retrieval with temporal comparisons.

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 concise with two sentences: one stating the purpose and another providing a clarifying note. It is front-loaded with the main functionality. However, the second sentence could be more tightly integrated, and there is some redundancy with schema information.

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

Completeness2/5

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

Given the tool's complexity (involving temporal analysis of referring domains for multiple targets), lack of annotations, and no output schema, the description is incomplete. It fails to explain key behavioral aspects like what 'new and lost' entails, how results are structured, or any limitations (e.g., data freshness, rate limits). The schema covers parameters well, but the overall context for effective tool use is lacking.

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 two parameters (targets and date_from). The description adds minimal value beyond the schema, only reiterating that targets can include domains, subdomains, and pages, and hinting at domain handling. It does not provide additional semantic context or usage examples not already in the schema descriptions.

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 the domains, subdomains and pages specified in the targets array.' It specifies the verb ('provide'), resource ('number of referring domains'), and targets, but does not explicitly differentiate from sibling tools like 'backlinks_bulk_referring_domains' or 'backlinks_bulk_new_lost_backlinks', which may offer similar or 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 Guidelines2/5

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

The description includes a note about how domains are handled (root domain vs. subdomains), but provides no guidance on when to use this tool versus alternatives. With many sibling tools in the 'backlinks' category, there is no explicit mention of when this tool is appropriate or when to choose other tools like 'backlinks_bulk_referring_domains' or 'backlinks_bulk_new_lost_backlinks'.

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