Skip to main content
Glama
ravinwebsurgeon

DataForSEO MCP Server

dataforseo_labs_search_intent

Analyze search intent for keywords to identify user goals as informational, navigational, commercial, or transactional with probability scores.

Instructions

This endpoint will provide you with search intent data for up to 1,000 keywords. For each keyword that you specify when setting a task, the API will return the keyword's search intent and intent probability. Besides the highest probable search intent, the results will also provide you with other likely search intent(s) and their probability. Based on keyword data and search results data, our system has been trained to detect four types of search intent: informational, navigational, commercial, transactional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsYestarget keywords required field UTF-8 encoding maximum number of keywords you can specify in this array: 1000
language_codeNolanguage code required field Note: this endpoint currently supports the following languages only: ar, zh-TW, cs, da, nl, en, fi, fr, de, he, hi, it, ja, ko, ms, nb, pl, pt, ro, ru, es, sv, th, uk, vi, bg, hr, sr, sl, bsen

Implementation Reference

  • The handle method implements the core tool logic by sending a POST request to the DataForSEO Labs API endpoint for Google search intent data using the provided keywords and language code, then processes the response or error.
    async handle(params: any): Promise<any> {
      try {
        const response = await this.client.makeRequest('/v3/dataforseo_labs/google/search_intent/live', 'POST', [{
          keywords: params.keywords,
          language_code: params.language_code
        }]);
        return this.validateAndFormatResponse(response);
      } catch (error) {
        return this.formatErrorResponse(error);
      }
    }
  • Zod schema defining the tool's input parameters: 'keywords' as an array of strings (up to 1000), and 'language_code' as a string defaulting to 'en' with supported languages listed.
      getParams(): z.ZodRawShape {
        return {
          keywords: z.array(z.string()).describe(`target keywords
    required field
    UTF-8 encoding
    maximum number of keywords you can specify in this array: 1000`),
          language_code: z.string().default("en").describe(
            `language code
            required field
            Note: this endpoint currently supports the following languages only:
    ar,
    zh-TW,
    cs,
    da,
    nl,
    en,
    fi,
    fr,
    de,
    he,
    hi,
    it,
    ja,
    ko,
    ms,
    nb,
    pl,
    pt,
    ro,
    ru,
    es,
    sv,
    th,
    uk,
    vi,
    bg,
    hr,
    sr,
    sl,
    bs`),
        };
      }
  • Registers the GoogleSearchIntentTool (line 43) along with other tools by instantiating them and adding to a record keyed by tool name, with description, params, and a wrapper around the handle method.
    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),
        },
      }), {});
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it processes up to 1,000 keywords, returns intent types (informational, navigational, commercial, transactional) with probabilities, and is based on trained system data. However, it lacks details on rate limits, authentication needs, error handling, or response format, which are important for a tool with no output schema.

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 well-structured and appropriately sized. It front-loads the core functionality, then elaborates on output details and intent types. Every sentence adds value, though it could be slightly more concise by integrating some details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is partially complete. It explains what the tool does and the intent types but lacks crucial context like response structure, error cases, or usage limits. This leaves gaps for an AI agent to invoke it correctly without additional information.

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 the 'keywords' and 'language_code' parameters. The description adds no additional parameter semantics beyond implying keyword processing, which is already covered. Baseline score of 3 is appropriate as the schema does the heavy lifting.

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 search intent data for up to 1,000 keywords' and specifies it returns 'search intent and intent probability' for each keyword. It distinguishes the tool by focusing on intent analysis rather than volume or location data, though it doesn't explicitly differentiate from all sibling tools by name.

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 tool's capabilities but doesn't indicate scenarios where it's appropriate, prerequisites, or comparisons to sibling tools like 'keywords_data_google_ads_search_volume' or 'dataforseo_labs_google_keyword_ideas'.

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