Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

keywords_data_dataforseo_trends_explore

Analyze keyword popularity trends for Google Search, News, and Shopping to inform SEO strategies and content planning.

Instructions

This endpoint will provide you with the keyword popularity data from DataForSEO Trends. You can check keyword trends for Google Search, Google News, and Google Shopping

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
location_nameNofull name of the location optional field in format "Country" example: United Kingdom
keywordsYeskeywords the maximum number of keywords you can specify: 5
typeNodataforseo trends typeweb
date_fromNostarting date of the time range if you don’t specify this field, the current day and month of the preceding year will be used by default minimal value for the web type: 2004-01-01 minimal value for other types: 2008-01-01 date format: "yyyy-mm-dd" example: "2019-01-15"
date_toNoending date of the time range if you don’t specify this field, the today’s date will be used by default date format: "yyyy-mm-dd" example: "2019-01-15"
time_rangeNopreset time ranges if you specify date_from or date_to parameters, this field will be ignored when setting a taskpast_7_days

Implementation Reference

  • The `handle` method executes the tool's core logic by sending a POST request to the DataForSEO Trends Explore API endpoint with the input parameters and handling the response or error.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.dataForSEOClient.makeRequest('/v3/keywords_data/dataforseo_trends/explore/live', 'POST', [{
          location_name: params.location_name,
          keywords: params.keywords,
          type: params.type,
          date_from: params.date_from,
          date_to: params.date_to,
          time_range: params.time_range,
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • The `getParams` method defines the Zod schema for validating the tool's input parameters, including location_name, keywords, type, date_from, date_to, and time_range.
    getParams(): z.ZodRawShape {
      return {
        location_name: z.string().nullable().default(null).describe(`full name of the location
          optional field
          in format "Country"
          example:
          United Kingdom`),
        keywords: z.array(z.string()).describe(`keywords
          the maximum number of keywords you can specify: 5`),
        type: z.enum(['web', 'news', 'ecommerce']).default('web').describe(`dataforseo trends type`),
        date_from: z.string().optional().describe(`starting date of the time range
            if you don’t specify this field, the current day and month of the preceding year will be used by default
            minimal value for the web type: 2004-01-01
            minimal value for other types: 2008-01-01
            date format: "yyyy-mm-dd"
            example:
            "2019-01-15"`),
        date_to: z.string().optional()
            .describe(
              `ending date of the time range
              if you don’t specify this field, the today’s date will be used by default
              date format: "yyyy-mm-dd"
              example:
              "2019-01-15"`),
        time_range: z.enum(['past_4_hours', 'past_day', 'past_7_days', 'past_30_days', 'past_90_days', 'past_12_months', 'past_5_years'])
            .default('past_7_days')
            .describe(
              `preset time ranges
              if you specify date_from or date_to parameters, this field will be ignored when setting a task`),
      };
    }
  • The `getTools` method in KeywordsDataApiModule instantiates the DataForSeoTrendsExploreTool and registers it into a tools record using its name, description, params, and a wrapper around its handle method.
    getTools(): Record<string, ToolDefinition> {
      const tools = [
        new GoogleAdsSearchVolumeTool(this.dataForSEOClient),
    
        new DataForSeoTrendsDemographyTool(this.dataForSEOClient),
        new DataForSeoTrendsSubregionInterestsTool(this.dataForSEOClient),
        new DataForSeoTrendsExploreTool(this.dataForSEOClient),
    
        new GoogleTrendsCategoriesTool(this.dataForSEOClient),
        new GoogleTrendsExploreTool(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),
        },
      }), {});
    }
  • Import statement for the DataForSeoTrendsExploreTool class used in registration.
    import { DataForSeoTrendsExploreTool } from './tools/dataforseo-trends/dataforseo-trends-explore.tool.js';
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. It mentions the data source (DataForSEO Trends) and scope (Google Search, News, Shopping), but fails to describe critical behaviors: whether this is a read-only operation, if it has rate limits, authentication requirements, error handling, or what the output format looks like (since no output schema exists). For a data query tool with 6 parameters, this is a significant gap.

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 purpose and scope. It's front-loaded with the main function. However, the second sentence could be more efficiently integrated, and there's some redundancy ('keyword trends' vs 'keyword popularity data'). Overall, it's efficient with minimal waste.

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 (6 parameters, no annotations, no output schema), the description is incomplete. It doesn't address behavioral aspects like rate limits or authentication, doesn't explain the output format, and provides no usage context relative to siblings. For a tool that fetches trend data with multiple configuration options, more contextual information is needed to guide effective use.

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%, meaning all parameters are well-documented in the schema itself. The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain relationships between parameters (e.g., how 'type' relates to the data sources mentioned) or provide usage examples. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't add value here.

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 keyword popularity data from DataForSEO Trends' and specifies the data sources (Google Search, News, Shopping). It uses specific verbs ('provide', 'check') and identifies the resource ('keyword popularity data'). However, it doesn't explicitly differentiate from sibling tools like 'keywords_data_google_trends_explore' or 'keywords_data_dataforseo_trends_demography', which likely serve related but distinct purposes.

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 mentions the data sources but doesn't indicate scenarios where this tool is preferred over sibling tools like 'keywords_data_google_trends_explore' or 'keywords_data_dataforseo_trends_demography'. There are no explicit when/when-not statements or named alternatives, leaving the agent without usage context.

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