Skip to main content
Glama
cortex8

DataForSEO MCP Server

by cortex8

backlinks_page_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.rank",">","80"] [["2.page_from_rank",">","55"], "and", ["1.original","=","true"]] [["1.first_seen",">","2017-10-23 11:31:45 +00:00"], "and", [["1.anchor","like","%seo%"],"or",["1.text_pre","not_like","%seo%"]]]
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: ["rank,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: ["domain_from_rank,desc","page_from_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 handler function that executes the core logic of the backlinks_page_intersection tool by making a POST request to the DataForSEO Backlinks API's page_intersection/live endpoint.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/backlinks/page_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);
      }
    }
  • Zod schema definition for the input parameters of the backlinks_page_intersection tool, including targets, 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.rank",">","80"]
    [["2.page_from_rank",">","55"],
    "and",
    ["1.original","=","true"]]
    
    [["1.first_seen",">","2017-10-23 11:31:45 +00:00"],
    "and",
    [["1.anchor","like","%seo%"],"or",["1.text_pre","not_like","%seo%"]]]`
          ),
          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:
    ["rank,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:
    ["domain_from_rank,desc","page_from_rank,asc"]`
          ),
        };
      }
  • Instantiation of the BacklinksPageIntersectionTool within the getTools() method's tools array.
    new BacklinksPageIntersectionTool(this.dataForSEOClient),
  • Generic registration logic in getTools() that maps each tool instance (including backlinks_page_intersection) to a ToolDefinition using its getName(), getDescription(), getParams(), and handle() methods.
    return tools.reduce((acc, tool) => ({
      ...acc,
      [tool.getName()]: {
        description: tool.getDescription(),
        params: tool.getParams(),
        handler: (params: any) => tool.handle(params),
      },
    }), {});
  • Helper mapping in BacklinksFiltersTool that associates the backlinks_page_intersection tool with the 'page_intersection' filter path for filter retrieval.
    'backlinks_page_intersection': 'page_intersection',
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the tool provides a 'list of domains' and hints at a 'Link Gap' use case, but doesn't disclose critical behavioral traits: whether this is a read-only operation, potential rate limits, authentication requirements, pagination behavior (beyond offset/limit parameters), or what format the returned data takes. The description adds minimal behavioral context beyond the basic purpose.

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 concise with two sentences. The first sentence states the core purpose, and the second provides a specific use case. Both sentences earn their place by adding value. However, the structure could be slightly improved by front-loading more operational details about the tool's behavior.

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 output schema, no annotations, and many similar sibling tools), the description is insufficiently complete. It doesn't explain what the output looks like, how results are structured, or how this tool differs from other backlinks tools. For a tool with this level of complexity and no structured output documentation, the description should provide more complete operational 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?

Schema description coverage is 100%, so the schema already thoroughly documents all 5 parameters. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it doesn't explain how 'targets' relates to the output, or provide additional context about filter usage. With complete schema coverage, the baseline is 3 even without parameter info in the description.

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.' This is a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its many sibling tools (like backlinks_domain_intersection or backlinks_referring_domains), which likely have overlapping functionality in the backlinks domain.

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 provides some usage context: '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 implies a competitive analysis use case but doesn't explicitly state when to use this tool versus alternatives among the many backlinks siblings, nor does it mention any prerequisites or exclusions.

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