Skip to main content
Glama
captainChaozi

Search Intent MCP

by captainChaozi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Intent MCP

请通过 https://aisearchintent.com 获取 API key

这是一个基于 MCP (Model Context Protocol) 的搜索意图分析服务。它可以帮助分析用户搜索关键词的意图，为 SEO 分析提供支持。

功能特点

  • 分析搜索关键词的意图

  • 提供可能的分类

  • 提供推理过程

  • 提供相关参考链接

  • 提供搜索建议

Related MCP server: SEO AI Assistant

使用方法

claude 安装

{
  "mcpServers": {
    "search_intent": {
      "command": "npx",
      "args": ["-y", "@search-intent/mcp"],
      "env": {
        "SEARCH_INTENT_API_KEY": "xxx"
      }
    }
  }
}

开发

# 克隆仓库
git clone

# 安装依赖
pnpm install

# 设置环境变量
export SEARCH_INTENT_API_KEY=your_api_key

API 使用示例

服务提供了一个名为 search_intent_analysis 的工具，可以这样使用：

{
  "name": "search_intent_analysis",
  "arguments": {
    "query": "grok3"
  }
}

返回结果示例：

{
  "query": "grok3",
  "intent": "Information Lookup about xAI's Grok 3...",
  "possibleCategories": [
    "AI Model",
    "Technology",
    "Chatbot",
    "Product Information"
  ],
  "reasoning": "The user is likely trying to understand...",
  "references": [
    {
      "url": "https://example.com",
      "title": "Example Title"
    }
  ],
  "searchSuggestions": [
    "grok3 meaning",
    "grok3 search intent",
    "grok3 categories",
    "grok3"
  ]
}

Available Tools

1 tool
search_intent_analysisC

A tool for analyzing search intent and user behavior.

Features:

  • Analyze search query intent

  • Identify relevant topic categories

  • Provide search suggestions

  • Offer reference links

Examples: "iphone 15" → Product research/purchase intent "python tutorial" → Learning intent

Response format:

  • query: Original search term

  • intent: Search intention

  • categories: Related categories

  • suggestions: Related search terms

  • references: Reference links

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesEnter a search term to analyze

TDQS

C2.5/5.0
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. It mentions features like analyzing intent and providing suggestions, but doesn't disclose behavioral traits such as rate limits, authentication needs, response time, or error handling. The examples and response format hint at output structure, but lack operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with sections like Features, Examples, and Response format, but includes redundant information (e.g., listing features that are somewhat repetitive). It could be more front-loaded; the core purpose is stated upfront, but subsequent details could be streamlined to avoid duplication.

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 no annotations, no output schema, and a single parameter with full schema coverage, the description is incomplete. It lacks details on behavioral aspects, error cases, and practical usage scenarios. The response format section partially compensates, but overall, it doesn't provide enough context for reliable tool invocation.

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%, with one parameter 'query' documented as 'Enter a search term to analyze'. The description adds no additional meaning beyond this, as it doesn't elaborate on parameter constraints, formats, or examples. Baseline score of 3 is appropriate since the schema adequately covers the parameter.

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 analyzes search intent and user behavior, which provides a general purpose. However, it lacks specificity about what resources it operates on (e.g., search queries, logs) and doesn't differentiate from siblings (though none exist). The phrase 'analyzing search intent' is somewhat vague without concrete examples of what analysis entails.

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 explicit guidance is provided on when to use this tool versus alternatives. The description lists features and examples, but these don't constitute usage instructions. Without sibling tools, there's no need for differentiation, but it still fails to specify prerequisites, constraints, or ideal scenarios for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedsearch_intent_analysis
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no ambiguity or overlap between tools. The tool has a clear, singular purpose focused on search intent analysis, making it impossible for an agent to misselect between non-existent alternatives.

Naming Consistency5/5

The single tool name follows a consistent snake_case pattern (search_intent_analysis). Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate.

Tool Count2/5

A single tool is too few for a server named 'Search Intent MCP', which suggests a broader scope for search-related operations. While the tool covers analysis well, the set lacks complementary tools for actions like refining searches, tracking trends, or managing intents, making it feel thin and incomplete for the domain.

Completeness2/5

The tool surface is severely incomplete for search intent analysis. It only provides analysis without supporting operations like saving intents, comparing queries over time, or integrating with search engines. This creates significant gaps that will limit agent workflows, as analysis alone is a dead end without follow-up actions.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • SEO AI Assistant

    ccnn2509
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides SEO automation with tools for keyword research, SERP analysis, and competitor analysis through Google Ads API integration, enabling AI assistants to access these capabilities via MCP.
    51
    -

  • SEO AI Assistant

    ayushsinghvi92
    F
    license
    Not graded
    quality
    D
    maintenance
    MCP server that enables AI assistants to perform SEO automation tasks including keyword research, SERP analysis, and competitor analysis through Google Ads API integration.
    1
    -

  • Google Search MCP Server

    Fabien-desablens
    A
    license
    A
    quality
    C
    maintenance
    An MCP server that provides Google Search functionality with automatic API key rotation and intelligent quota management, enabling natural language search queries with advanced filtering options.
    1
    7 npm
    1
    MIT

  • keyso-mcp

    abukreev-dev
    F
    license
    Not graded
    quality
    C
    maintenance
    MCP server for Keys.so SEO API, enabling domain and keyword analysis, competitor research, and SEO metrics retrieval through natural language.
    4
    -

Appeared in Searches