Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

dataforseo_labs_google_subdomains

Analyze subdomains of any domain to see their search ranking distribution and estimated traffic volume from Google organic and paid results.

Instructions

This endpoint will provide you with a list of subdomains of the specified domain, along with the ranking distribution across organic and paid search. In addition to that, you will also get the estimated traffic volume of subdomains based on search volume.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYestarget domain
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: ["metrics.organic.count",">",50] [["metrics.organic.pos_1","<>",0],"and",["metrics.organic.impressions_etv",">=","10"]] [[["metrics.organic.count",">=",50],"and",["metrics.organic.pos_1","in",[1,5]]],"or",["metrics.organic.etv",">=","100"]]
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 specify a sorting type example: ["metrics.paid.etv,asc"] Note: you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ["metrics.organic.etv,desc","metrics.paid.count,asc"] default rule: ["metrics.organic.count,desc"]
item_typesNodisplay results by item type indicates the type of search results included in the response
include_clickstream_dataNoInclude or exclude data from clickstream-based metrics in the result

Implementation Reference

  • The GoogleSubdomainsTool class implements the tool, including name, description, input schema (getParams), and the handle method that makes the DataForSEO API request to '/v3/dataforseo_labs/google/subdomains/live'.
    export class GoogleSubdomainsTool extends BaseTool {
      constructor(private client: DataForSEOClient) {
        super(client);
      }
    
      getName(): string {
        return 'dataforseo_labs_google_subdomains';
      }
    
      getDescription(): string {
        return `This endpoint will provide you with a list of subdomains of the specified domain, along with the ranking distribution across organic and paid search. In addition to that, you will also get the estimated traffic volume of subdomains based on search volume.`;
      }
    
      getParams(): z.ZodRawShape {
        return {
          target: z.string().describe(`target domain`),
          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:
            ["metrics.organic.count",">",50]
            [["metrics.organic.pos_1","<>",0],"and",["metrics.organic.impressions_etv",">=","10"]]
            [[["metrics.organic.count",">=",50],"and",["metrics.organic.pos_1","in",[1,5]]],"or",["metrics.organic.etv",">=","100"]]`
          ),
          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 specify a sorting type
    example:
    ["metrics.paid.etv,asc"]
    Note: you can set no more than three sorting rules in a single request
    you should use a comma to separate several sorting rules
    example:
    ["metrics.organic.etv,desc","metrics.paid.count,asc"]
    default rule:
    ["metrics.organic.count,desc"]`
          ),
          item_types: z.array(z.string()).optional().describe(
            `item types to return
            optional field
            default: ['organic']
            possible values:
            organic
            paid`
          ),
          include_clickstream_data: z.boolean().optional().default(false).describe(
            `Include or exclude data from clickstream-based metrics in the result`)
    
        };
      }
    
      async handle(params: any): Promise<any> {
        try {
          const response = await this.client.makeRequest('/v3/dataforseo_labs/google/subdomains/live', 'POST', [{
            target: params.target,
            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: params.item_types,
            include_clickstream_data: params.include_clickstream_data,
            limit: params.limit,
            offset: params.offset
          }]);
          return this.validateAndFormatResponse(response);
        } catch (error) {
          return this.formatErrorResponse(error);
        }
      }
  • The DataForSEOLabsApi module registers the GoogleSubdomainsTool by instantiating it and adding to the tools record returned by getTools(), mapping name to description, params, and handler.
    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),
        },
      }), {});
    }
  • Mapping of the tool name to its filter path 'subdomains.google' used in the labs filters tool for providing filter information.
    private static readonly TOOL_TO_FILTER_MAP: { [key: string]: string } = {
      'dataforseo_labs_google_ranked_keywords': 'ranked_keywords.google',
      'dataforseo_labs_google_keyword_ideas': 'keyword_ideas.google',
      'dataforseo_labs_google_keywords_for_site': 'keywords_for_site.google',
      'dataforseo_labs_google_competitors_domain': 'competitors_domain.google',
      'dataforseo_labs_google_serp_competitors': 'serp_competitors.google',
      'dataforseo_labs_google_subdomains': 'subdomains.google',
      'dataforseo_labs_google_domain_intersection': 'domain_intersection.google',
      'dataforseo_labs_google_page_intersection': 'page_intersection.google',
      'dataforseo_labs_google_historical_serp': 'historical_serp.google',
      'dataforseo_labs_google_historical_rank_overview': 'domain_rank_overview.google',
      'dataforseo_labs_google_relevant_pages': 'relevant_pages.google',
      'dataforseo_labs_google_top_searches': 'top_searches.google',
      'dataforseo_labs_google_keyword_overview': 'keyword_overview.google',
      'dataforseo_labs_google_search_intent': 'search_intent.google',
      'dataforseo_labs_google_bulk_keyword_difficulty': 'bulk_keyword_difficulty.google',
      'dataforseo_labs_google_related_keywords': 'related_keywords.google',
      'dataforseo_labs_google_keyword_suggestions': 'keyword_suggestions.google',
      'dataforseo_labs_google_domain_rank_overview': 'domain_rank_overview.google',
      'dataforseo_labs_google_domain_metrics_by_categories': 'domain_metrics_by_categories.google',
      'dataforseo_labs_google_domain_whois_overview': 'domain_whois_overview.google',
      'dataforseo_labs_google_categories_for_domain': 'categories_for_domain.google',
      'dataforseo_labs_google_keywords_for_categories': 'keywords_for_categories.google',
      'dataforseo_labs_amazon_product_competitors': 'product_competitors.amazon',
      'dataforseo_labs_amazon_product_keyword_intersections': 'product_keyword_intersections.amazon',
      'dataforseo_labs_google_app_competitors': 'app_competitors.google',
      'dataforseo_labs_apple_app_competitors': 'app_competitors.apple',
      'dataforseo_labs_google_app_intersection': 'app_intersection.google',
      'dataforseo_labs_apple_app_intersection': 'app_intersection.apple',
      'dataforseo_labs_google_keywords_for_app': 'keywords_for_app.google',
      'dataforseo_labs_apple_keywords_for_app': 'keywords_for_app.apple',
      'dataforseo_labs_database_rows_count': 'database_rows_count'
    };
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 what data is returned (subdomains, ranking distribution, traffic estimates) but lacks critical behavioral details: whether this is a read-only operation, rate limits, authentication requirements, data freshness, or error conditions. For a tool with 10 parameters and no annotations, this is a significant gap in transparency.

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—two sentences that directly state the tool's core functionality. It's front-loaded with the primary purpose and avoids unnecessary elaboration. However, it could be slightly more structured by explicitly separating outputs (subdomains, ranking, traffic) for clarity.

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 (10 parameters, no output schema, no annotations), the description is incomplete. It lacks information on return format, pagination, error handling, and usage context. Without annotations or output schema, the description should provide more behavioral and operational details to guide the agent effectively.

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 all 10 parameters. The description adds no parameter-specific information beyond what's in the schema—it doesn't explain how 'target' relates to subdomains, or how 'filters' apply to the results. With high schema coverage, the baseline is 3, and the description doesn't compensate with additional semantic context.

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 a list of subdomains of the specified domain, along with the ranking distribution across organic and paid search' and 'estimated traffic volume of subdomains'. It specifies the verb ('provide'), resource ('subdomains'), and key outputs. However, it doesn't explicitly differentiate from sibling tools like 'dataforseo_labs_google_domain_rank_overview' or 'dataforseo_labs_google_competitors_domain', which might offer 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, limitations, or compare it to sibling tools like 'dataforseo_labs_google_domain_intersection' or 'dataforseo_labs_google_ranked_keywords'. The agent must infer usage from the purpose alone, which is insufficient for optimal tool selection.

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