Search Intent MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARCH_INTENT_API_KEY | Yes | API key obtained from https://aisearchintent.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_intent_analysisC | A tool for analyzing search intent and user behavior. Features:
Examples: "iphone 15" → Product research/purchase intent "python tutorial" → Learning intent Response format:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.