google-alerts-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_google_alertsC | Search Google Alerts for news articles about a specific topic by simulating the browser workflow |
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
Only one tool exists, so there is no possibility of ambiguity between tools.
The single tool uses a clear verb_noun pattern (search_google_alerts), consistent with best practices.
One tool is slightly thin for a server named 'google-alerts-mcp', but it covers the core search functionality reasonably well without being overblown.
The server only provides search functionality, missing obvious operations like creating, listing, or deleting alerts, which limits its completeness.