Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

keywords_data_dataforseo_trends_subregion_interests

Analyze keyword popularity trends across specific locations and time periods to inform SEO strategies and content planning.

Instructions

This endpoint will provide you with location-specific keyword popularity data from DataForSEO Trends

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 implements the core logic of the tool. It makes a POST request to the DataForSEO API endpoint '/v3/keywords_data/dataforseo_trends/subregion_interests/live' with the input parameters wrapped in an array, then validates and formats the response or handles errors.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.dataForSEOClient.makeRequest('/v3/keywords_data/dataforseo_trends/subregion_interests/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);
      }
    }
  • Defines the input schema using Zod shapes for parameters: location_name, keywords, type, date_from, date_to, 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 DataForSeoTrendsSubregionInterestsTool (line 15) along with other tools and registers them by name into a record used for tool definitions, including description, params, and handler wrappers.
    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),
        },
      }), {});
    }
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 'provide you with location-specific keyword popularity data', implying a read-only operation, but fails to detail critical aspects like authentication needs, rate limits, error handling, or data format. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence that efficiently states the tool's purpose without unnecessary details. It's front-loaded and appropriately sized, though it could be slightly more informative without losing conciseness.

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 of 6 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral traits, output format, and usage context, making it incomplete for effective tool invocation by an AI agent.

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 6 parameters. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or use cases. The baseline score of 3 reflects adequate coverage by the schema alone.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool provides 'location-specific keyword popularity data from DataForSEO Trends', which clarifies it's a data retrieval tool for keyword trends. However, it doesn't specify the exact verb (e.g., 'fetch' or 'retrieve') or differentiate from siblings like 'keywords_data_dataforseo_trends_demography' or 'keywords_data_dataforseo_trends_explore', leaving the scope somewhat vague.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about use cases, prerequisites, or comparisons to sibling tools, leaving the agent without direction on 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