Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

dataforseo_labs_google_domain_intersection

Find keywords where two domains rank together in Google search results. Get search volume, competition, CPC, and traffic data for each shared keyword to analyze competitive overlap and opportunities.

Instructions

This endpoint will provide you with the keywords for which both specified domains rank within the same SERP. You will get search volume, competition, cost-per-click and impressions data on each intersecting keyword. Along with that, you will get data on the first and second domain's SERP element discovered for this keyword, as well as the estimated traffic volume and cost of ad traffic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target1Yestarget domain 1
target2Yestarget domain 2
location_nameNofull name of the location required field only in format "Country" (not "City" or "Region") example: 'United Kingdom', 'United States', 'Canada'United States
language_codeNolanguage code required field example: enen
ignore_synonymsNoignore highly similar keywords, if set to true, results will be more accurate
limitNoMaximum number of keywords to return
offsetNooffset in the results array of returned keywords optional field default value: 0 if you specify the 10 value, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords
filtersNoyou 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, match, not_match, ilike, not_ilike, like, not_like you can use the % operator with like and not_like, as well as ilike and not_ilike to match any string of zero or more characters merge operator must be a string and connect two other arrays, availible values: or, and. example: ["keyword_data.keyword_info.search_volume","in",[100,1000]] [["first_domain_serp_element.etv",">",0],"and",["first_domain_serp_element.description","like","%goat%"]] [["keyword_data.keyword_info.search_volume",">",100],"and",[["first_domain_serp_element.description","like","%goat%"],"or",["second_domain_serp_element.type","=","organic"]]]
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 parameter example: ["keyword_data.keyword_info.competition,desc"] default rule: ["keyword_data.keyword_info.search_volume,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: ["keyword_data.keyword_info.search_volume,desc","keyword_data.keyword_info.cpc,desc"]
intersectionsNodomain intersections in SERP optional field if you set intersections to true, you will get the keywords for which both target domains specified as target1 and target2 have results within the same SERP; the corresponding SERP elements for both domains will be provided in the results array Note: this endpoint will not provide results if the number of intersecting keywords exceeds 10 million if you specify intersections: false, you will get the keywords for which the domain specified as target1 has results in SERP, and the domain specified as target2 doesn’t; thus, the corresponding SERP elements and other data will be provided for the domain specified as target1only default value: true
include_clickstream_dataNoInclude or exclude data from clickstream-based metrics in the result
item_typesNodisplay results by item type indicates the type of search results included in the response

Implementation Reference

  • The handle method that executes the core tool logic by sending a POST request to the DataForSEO Labs Google Domain Intersection API endpoint and processing the response.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/dataforseo_labs/google/domain_intersection/live', 'POST', [{
          target1: params.target1,
          target2: params.target2,
          location_name: params.location_name,
          language_code: params.language_code,
          ignore_synonyms: params.ignore_synonyms,
          filters: this.formatFilters(params.filters),
          order_by: this.formatOrderBy(params.order_by),
          exclude_top_domains: params.exclude_top_domains,
          item_types: ['organic'],
          intersections: params.intersections,
          include_clickstream_data: params.include_clickstream_data,
          limit: params.limit,
          offset: params.offset
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Zod schema definition for the tool's input parameters in the getParams method.
      getParams(): z.ZodRawShape {
        return {
          target1: z.string().describe(`target domain 1`),
          target2: z.string().describe(`target domain 2 `),
          location_name: z.string().default("United States").describe(`full name of the location
    required field
    in format "Country"
    example:
    United Kingdom`),
          language_code: z.string().default("en").describe(
            `language code
            required field
            example:
            en`),
          ignore_synonyms: z.boolean().default(true).describe(
              `ignore highly similar keywords, if set to true, results will be more accurate`),
          limit: z.number().min(1).max(1000).default(10).optional().describe("Maximum number of keywords to return"),
          offset: z.number().min(0).optional().describe(
            `offset in the results array of returned keywords
            optional field
            default value: 0
            if you specify the 10 value, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords`
          ),
          filters: z.array(
            z.union([
              z.array(z.union([z.string(), z.number(), z.boolean()])).length(3),
              z.enum(["and", "or"])
            ])
          ).max(8).optional().describe(
            `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, match, not_match, ilike, not_ilike, like, not_like
            you can use the % operator with like and not_like, as well as ilike and not_ilike to match any string of zero or more characters
            merge operator must be a string and connect two other arrays, availible values: or, and.
            example:
            ["keyword_data.keyword_info.search_volume","in",[100,1000]]
            [["first_domain_serp_element.etv",">",0],"and",["first_domain_serp_element.description","like","%goat%"]]
            [["keyword_data.keyword_info.search_volume",">",100],"and",[["first_domain_serp_element.description","like","%goat%"],"or",["second_domain_serp_element.type","=","organic"]]]`
          ),
          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 parameter
    example:
    ["keyword_data.keyword_info.competition,desc"]
    default rule:
    ["keyword_data.keyword_info.search_volume,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:
    ["keyword_data.keyword_info.search_volume,desc","keyword_data.keyword_info.cpc,desc"]`
          ),
          intersections: z.boolean().optional().describe(`domain intersections in SERP
    optional field
    if you set intersections to true, you will get the keywords for which both target domains specified as target1 and target2 have results within the same SERP; the corresponding SERP elements for both domains will be provided in the results array
    Note: this endpoint will not provide results if the number of intersecting keywords exceeds 10 million
    if you specify intersections: false, you will get the keywords for which the domain specified as target1 has results in SERP, and the domain specified as target2 doesn’t;
    thus, the corresponding SERP elements and other data will be provided for the domain specified as target1only
    default value: true`).default(true),
          include_clickstream_data: z.boolean().optional().default(false).describe(
            `Include or exclude data from clickstream-based metrics in the result`)
    
    
        };
      }
  • Registration of the GoogleDomainIntersectionsTool instance within the DataForSEOLabsApi module's getTools method, which returns a map of all tools by name including handler, schema, and description.
    getTools(): Record<string, ToolDefinition> {
      const tools = [
        new GoogleRankedKeywordsTool(this.dataForSEOClient),
        new GoogleDomainCompetitorsTool(this.dataForSEOClient),
        new GoogleDomainRankOverviewTool(this.dataForSEOClient),
        new GoogleKeywordsIdeasTool(this.dataForSEOClient),
        new GoogleRelatedKeywordsTool(this.dataForSEOClient),
        new GoogleKeywordsSuggestionsTool(this.dataForSEOClient),
        new GoogleHistoricalSERP(this.dataForSEOClient),
        new GoogleSERPCompetitorsTool(this.dataForSEOClient),
        new GoogleBulkKeywordDifficultyTool(this.dataForSEOClient),
        new GoogleSubdomainsTool(this.dataForSEOClient),
        new GoogleKeywordOverviewTool(this.dataForSEOClient),
        new GoogleTopSearchesTool(this.dataForSEOClient),
        new GoogleSearchIntentTool(this.dataForSEOClient),
        new GoogleKeywordsForSiteTool(this.dataForSEOClient),
        new GoogleDomainIntersectionsTool(this.dataForSEOClient),
        new GoogleHistoricalDomainRankOverviewTool(this.dataForSEOClient),
        new GooglePageIntersectionsTool(this.dataForSEOClient),
        new GoogleBulkTrafficEstimationTool(this.dataForSEOClient),
        new DataForSeoLabsFilterTool(this.dataForSEOClient),
        new GoogleHistoricalKeywordDataTool(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),
        },
      }), {});
    }
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. It mentions the data returned (e.g., search volume, traffic estimates) but fails to disclose critical behavioral traits: it does not specify if this is a read-only or mutating operation, rate limits, authentication needs, or error conditions. The schema hints at a 10-million keyword limit, but the description does not surface this, leaving gaps in transparency for a complex 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 front-loaded with the core purpose in the first sentence, followed by details on returned data. It uses two sentences efficiently, with no redundant information. However, it could be slightly more structured by separating usage context from data details, but overall it is concise and well-organized.

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 (12 parameters, no annotations, no output schema), the description is inadequate. It explains what the tool does but lacks context on behavioral aspects (e.g., safety, performance), output structure, or error handling. Without annotations or an output schema, the description should compensate more to guide effective use, but it falls short, leaving significant gaps for agent invocation.

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 all 12 parameters thoroughly. The description adds no specific parameter semantics beyond implying the use of 'target1' and 'target2' for domains. It does not explain parameter interactions or provide examples beyond what the schema offers, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 keywords for which both specified domains rank within the same SERP.' It specifies the verb ('provide'), resource ('keywords'), and scope ('both specified domains rank within the same SERP'), distinguishing it from sibling tools like 'dataforseo_labs_google_keywords_for_site' or 'dataforseo_labs_google_page_intersection' by focusing on domain intersection in SERP rankings.

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 for comparing two domains' keyword rankings and provides some context about the data returned (e.g., search volume, SERP elements). However, it lacks explicit guidance on when to use this tool versus alternatives like 'dataforseo_labs_google_competitors_domain' or 'dataforseo_labs_google_ranked_keywords', and does not mention prerequisites or exclusions, such as the 10-million keyword limit noted in the schema.

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