Google Trends MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_TRENDS_API_KEY | No | Your RapidAPI key for the Google Trends Scraper API (optional, defaults to example key). |
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 |
|---|---|
| google_trends_statusC | Check the status of the Google Trends API |
| google_trends_questionsC | Get trending questions from Google Trends |
| google_trends_trendingB | Get currently trending topics from Google Trends |
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 3 tools
Each tool has a clearly distinct purpose: one for trending questions, one for API status, and one for currently trending topics. There is no overlap or ambiguity.
All tools follow a consistent `google_trends_<noun>` pattern, with clear, descriptive names. The verb (get) is implied, and the naming is uniform.
Three tools is minimal but reasonable for a focused server. The count covers the core functionalities—trending topics, related questions, and status—without being excessive.
The server covers basic features like trending topics and questions but lacks tools for specific search queries (e.g., interest over time, comparisons). The surface is functional but not comprehensive.