Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

dataforseo_labs_google_keyword_overview

Analyze Google keyword metrics including search volume, CPC, competition, and intent to optimize SEO strategies and paid search campaigns.

Instructions

This endpoint provides Google keyword data for specified keywords. For each keyword, you will receive current cost-per-click, competition values for paid search, search volume, search intent, monthly searches

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsYeskeywords required field The maximum number of keywords you can specify: 700 The maximum number of characters for each keyword: 80 The maximum number of words for each keyword phrase: 10 the specified keywords will be converted to lowercase format, data will be provided in a separate array note that if some of the keywords specified in this array are omitted in the results you receive, then our database doesn't contain such keywords and cannot return data on them you will not be charged for the keywords omitted in the results
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
include_clickstream_dataNoInclude or exclude data from clickstream-based metrics in the result

Implementation Reference

  • The handler function that executes the core logic: sends POST request to DataForSEO Labs API endpoint '/v3/dataforseo_labs/google/keyword_overview/live' with parameters and formats the response.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/dataforseo_labs/google/keyword_overview/live', 'POST', [{
          keywords: params.keywords,
          location_name: params.location_name,
          language_code: params.language_code,
          include_clickstream_data: params.include_clickstream_data
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Zod schema definition for input parameters: keywords (array), location_name, language_code, include_clickstream_data.
      getParams(): z.ZodRawShape {
        return {
          keywords: z.array(z.string()).describe(`keywords
    required field
    The maximum number of keywords you can specify: 700
    The maximum number of characters for each keyword: 80
    The maximum number of words for each keyword phrase: 10
    the specified keywords will be converted to lowercase format, data will be provided in a separate array
    note that if some of the keywords specified in this array are omitted in the results you receive, then our database doesn't contain such keywords and cannot return data on them
    you will not be charged for the keywords omitted in the results`),
          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`),
          include_clickstream_data: z.boolean().optional().default(false).describe(
            `Include or exclude data from clickstream-based metrics in the result`)
        };
      }
  • Tool class is instantiated with 'new GoogleKeywordOverviewTool(this.dataForSEOClient)' and registered in the getTools() method of DataForSEOLabsApi module, 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),
        },
      }), {});
    }
  • Instantiation of the GoogleKeywordOverviewTool class.
    new GoogleKeywordOverviewTool(this.dataForSEOClient),
  • Mapping of tool name to filter path in DataForSeoLabsFilterTool for available filters.
    'dataforseo_labs_google_keyword_overview': 'keyword_overview.google',
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 for behavioral disclosure. While it mentions what data is returned, it doesn't address important behavioral aspects: whether this is a read-only operation, potential costs/rate limits, data freshness, authentication requirements, or error conditions. The description is purely functional without operational context that would help an agent use it appropriately.

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 - a single sentence that efficiently lists the key data points returned. It's front-loaded with the core purpose and doesn't waste words. However, it could be slightly more structured by separating the tool's function from the data points returned 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?

Given the complexity (keyword analysis tool with 4 parameters), no annotations, and no output schema, the description is incomplete. It doesn't explain the return format, data structure, or what happens when keywords aren't found (though the schema mentions this). For a data retrieval tool with multiple parameters and no output schema, the description should provide more context about the response format and operational considerations.

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 fully documents all 4 parameters. The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description. The description doesn't compensate or add value regarding parameters.

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: 'provides Google keyword data for specified keywords' and lists specific data points (cost-per-click, competition, search volume, intent, monthly searches). It distinguishes itself from siblings by focusing on keyword overview data rather than historical data, keyword ideas, or other specialized functions. However, it doesn't explicitly contrast with similar tools like 'keywords_data_google_ads_search_volume' or 'dataforseo_labs_google_historical_keyword_data'.

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 available (including 'keywords_data_google_ads_search_volume', 'dataforseo_labs_google_historical_keyword_data', 'dataforseo_labs_google_keyword_ideas'), there's no indication of when this 'overview' tool is appropriate versus those other keyword data tools. The description simply states what data is returned without contextual usage advice.

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