Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

dataforseo_labs_google_keywords_for_site

Analyze a website's organic search performance by discovering relevant keywords with monthly search volume, CPC, and competition data to identify optimization opportunities.

Instructions

The Keywords For Site endpoint will provide you with a list of keywords relevant to the target domain. Each keyword is supplied with relevant, search volume data for the last month, cost-per-click, competition

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
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_info.search_volume",">",0] [["keyword_info.search_volume","in",[0,1000]], "and", ["keyword_info.competition_level","=","LOW"]][["keyword_info.search_volume",">",100], "and", [["keyword_info.cpc","<",0.5], "or", ["keyword_info.high_top_of_page_bid","<=",0.5]]]
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 default rule: ["relevance,desc"] example: ["relevance,desc","keyword_info.search_volume,desc"]
include_subdomainsNoInclude keywords from subdomains
include_clickstream_dataNoInclude or exclude data from clickstream-based metrics in the result

Implementation Reference

  • The `handle` method that executes the tool's core logic: sends a POST request to the DataForSEO Labs `/v3/dataforseo_labs/google/keywords_for_site/live` endpoint with formatted parameters and handles the response or error.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/dataforseo_labs/google/keywords_for_site/live', 'POST', [{
          target: params.target,
          location_name: params.location_name,
          language_code: params.language_code,
          limit: params.limit,
          offset: params.offset,
          filters: this.formatFilters(params.filters),
          order_by: this.formatOrderBy(params.order_by),
          include_subdomains: params.include_subdomains,
          include_clickstream_data: params.include_clickstream_data
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • The `getParams` method provides the Zod schema for input parameter validation, defining types, defaults, and descriptions for all supported parameters.
      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`),
          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_info.search_volume",">",0]
    [["keyword_info.search_volume","in",[0,1000]],
    "and",
    ["keyword_info.competition_level","=","LOW"]][["keyword_info.search_volume",">",100],
    "and",
    [["keyword_info.cpc","<",0.5],
    "or",
    ["keyword_info.high_top_of_page_bid","<=",0.5]]]`
          ),
          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
    default rule:
    ["relevance,desc"]
    example:
    ["relevance,desc","keyword_info.search_volume,desc"]`,
          ),
          include_subdomains: z.boolean().optional().describe("Include keywords from subdomains"),
          include_clickstream_data: z.boolean().optional().default(false).describe(
            `Include or exclude data from clickstream-based metrics in the result`)
        };
      }
  • The `getTools` method in the DataForSEOLabsApi module instantiates the GoogleKeywordsForSiteTool (line 44) and registers it along with other tools by creating a record mapping tool names to their descriptions, parameters, and handlers.
    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 'keywords_for_site.google' used in the DataForSeoLabsFilterTool for providing filter information.
    'dataforseo_labs_google_keywords_for_site': 'keywords_for_site.google',
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the type of data returned (search volume, CPC, competition) but doesn't cover important behavioral aspects like whether this is a read-only operation, rate limits, authentication requirements, data freshness (it mentions 'last month' but not update frequency), pagination behavior (implied by offset/limit but not explained), or error conditions. For a tool with 9 parameters and no annotations, this is inadequate.

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 a single, efficient sentence that states the core functionality. It's appropriately sized and front-loaded with the main purpose. However, it could be slightly more structured by separating the purpose from the data details for better readability.

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?

For a tool with 9 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the tool's behavioral characteristics, usage context, or output format. While the schema covers parameters well, the description fails to provide the broader context needed for an AI agent to use this tool effectively, especially given the complex sibling tool landscape.

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 9 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. It mentions the data fields returned (search volume, CPC, competition) which relate to output, not input parameters. Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 keywords relevant to the target domain' with specific data fields (search volume, cost-per-click, competition). It uses a specific verb ('provide') and resource ('keywords'), but doesn't explicitly differentiate from sibling tools like 'dataforseo_labs_google_keyword_ideas' or 'dataforseo_labs_google_related_keywords' that might have 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. With many sibling tools in the 'dataforseo_labs_google_' category (e.g., keyword_ideas, related_keywords, ranked_keywords), there's no indication of how this tool differs or when it's the appropriate choice. The description only states what it does, not when to use it.

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