mcp-search-linkup
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKUP_API_KEY | Yes | Your Linkup API key (required) |
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-webA | Search the web in real time using Linkup. Use this tool whenever the user needs trusted facts, news, or source-backed information. Returns comprehensive content from the most relevant sources. |
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 possibility of ambiguity or overlap between tools. The tool 'search-web' has a clear, distinct purpose focused on web searching.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'search-web' follows a clear verb-noun pattern and is straightforward.
A single tool is too few for most server purposes, as it severely limits functionality and scope. This feels thin and incomplete for a search-oriented server, lacking operations like filtering, advanced queries, or result management.
The server has a significant gap in its tool surface; it only provides search functionality without any way to refine, save, or manage results. For a search domain, this is incomplete and will likely cause agent failures in complex tasks.