Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_domain_intersection

Identify domains that link to your competitors but not to your website to uncover link building opportunities and analyze competitive backlink gaps.

Instructions

This endpoint will provide you with the list of domains pointing to the specified websites. This endpoint is especially useful for creating a Link Gap feature that shows what domains link to your competitors but do not link out to your website

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersNoarray of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, <>, in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: ["1.internal_links_count",">","1"] [["2.referring_pages",">","2"], "and", ["1.backlinks",">","10"]] [["1.first_seen",">","2017-10-23 11:31:45 +00:00"], "and", [["2.target","like","%dataforseo.com%"],"or",["1.referring_domains",">","10"]]]
limitNothe maximum number of returned results
offsetNooffset in the array of returned results optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks
order_byNoresults sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: ["backlinks,desc"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ["backlinks,desc","rank,asc"]
targetsYesdomains, subdomains or webpages to get links for required field you can set up to 20 domains, subdomains or webpages a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)

Implementation Reference

  • The handle method implements the tool's core logic, making a POST request to DataForSEO's domain_intersection endpoint with processed parameters and handling response or error.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/domain_intersection/live', 'POST', [{
          targets: mapArrayToNumberedKeys(params.targets),
          limit: params.limit,
          offset: params.offset,
          filters: this.formatFilters(params.filters),
          order_by: this.formatOrderBy(params.order_by),
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Defines the Zod schema for the tool's input parameters: targets (required array of strings), limit, offset, filters, and order_by.
      getParams(): z.ZodRawShape {
        return {
          targets: z.array(z.string()).describe(`domains, subdomains or webpages to get links for
    required field
    you can set up to 20 domains, subdomains or webpages
    a domain or a subdomain should be specified without https:// and www.
    a page should be specified with absolute URL (including http:// or https://)`),
          limit: z.number().min(1).max(1000).default(10).optional().describe("the maximum number of returned results"),
          offset: z.number().min(0).optional().describe(
            `offset in the array of returned results
    optional field
    default value: 0
    if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks`
          ),
          filters: this.getFilterExpression().optional().describe(
            `array of results filtering parameters
    optional field
    you can add several filters at once (8 filters maximum)
    you should set a logical operator and, or between the conditions
    the following operators are supported:
    regex, not_regex, =, <>, in, not_in, like, not_like, ilike, not_ilike, match, not_match
    you can use the % operator with like and not_like to match any string of zero or more characters
    example:
    ["1.internal_links_count",">","1"]
    [["2.referring_pages",">","2"],
    "and",
    ["1.backlinks",">","10"]]
    
    [["1.first_seen",">","2017-10-23 11:31:45 +00:00"],
    "and",
    [["2.target","like","%dataforseo.com%"],"or",["1.referring_domains",">","10"]]]`
          ),
          order_by: z.array(z.string()).optional().describe(
            `results sorting rules
    optional field
    you can use the same values as in the filters array to sort the results
    possible sorting types:
    asc – results will be sorted in the ascending order
    desc – results will be sorted in the descending order
    you should use a comma to set up a sorting type
    example:
    ["backlinks,desc"]
    note that you can set no more than three sorting rules in a single request
    you should use a comma to separate several sorting rules
    example:
    ["backlinks,desc","rank,asc"]`
          ),
        };
      }
  • Registers the backlinks_domain_intersection tool (line 42: new BacklinksDomainIntersectionTool) among others by creating instances and reducing them into a tool definition record with name, 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),
        },
      }), {});
    }
  • Static map in BacklinksFiltersTool that associates 'backlinks_domain_intersection' with filter path 'domain_intersection' for filter handling.
    private static readonly TOOL_TO_FILTER_MAP: { [key: string]: string } = {
      'backlinks_content_duplicates': 'content_duplicates',
      'backlinks_backlinks': 'backlinks',
      'backlinks_domain_pages': 'domain_pages',
      'backlinks_anchors': 'anchors',
      'backlinks_referring_domains': 'referring_domains',
      'backlinks_domain_intersection': 'domain_intersection',
      'backlinks_page_intersection': 'page_intersection',
      'backlinks_referring_networks': 'referring_networks',
      'backlinks_domain_pages_summary': 'domain_pages_summary',
      'backlinks_competitors': 'competitors'
    };
  • Returns the canonical tool name 'backlinks_domain_intersection' used for registration.
    getName(): string {
      return 'backlinks_domain_intersection';
    }
Behavior2/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 mentions the tool's purpose and a use case but lacks critical behavioral details: it doesn't specify whether this is a read-only operation, what authentication is required, rate limits, pagination behavior (beyond what's in the schema), or what the output format looks like. For a tool with 5 parameters and no output schema, this is a significant gap.

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 sentence states the core purpose, and the second provides valuable context about the Link Gap use case. Both sentences earn their place by adding meaningful information beyond the tool name. It could be slightly more structured but is efficient overall.

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 complexity (5 parameters, no annotations, no output schema), the description is incomplete. It explains the purpose and a use case but doesn't address critical behavioral aspects like authentication needs, rate limits, error conditions, or what the return data looks like. For a backlink analysis tool with filtering and sorting capabilities, more context about the operation's nature and output is needed.

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 schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. It mentions 'specified websites' which aligns with the 'targets' parameter but doesn't provide additional semantic context. Baseline 3 is appropriate when the schema does the heavy lifting.

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 list of domains pointing to the specified websites.' It specifies the verb ('provide') and resource ('domains pointing to websites'), and distinguishes it from siblings by mentioning its specific use case for 'Link Gap' analysis. However, it doesn't explicitly differentiate from similar-sounding siblings like 'backlinks_referring_domains' or 'backlinks_competitors'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: 'especially useful for creating a Link Gap feature that shows what domains link to your competitors but do not link out to your website.' This gives a specific scenario (competitive analysis) and implies usage for intersection analysis. However, it doesn't explicitly state when not to use it or name alternatives among the many sibling 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/cortex8/oyt-dataforseo-mcp-worker'

If you have feedback or need assistance with the MCP directory API, please join our Discord server