Google Trends Scraper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_google_trendsA | Read Google Trends for search terms: a summary per term (average, latest, and peak interest, recent change, top region, top and rising queries) plus flat rows for interest over time, by region, metro, or city, and related queries. Values are relative 0 to 100, not search counts. Compare up to 5 terms on one scale. No Google account or key. |
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
There is only one tool, so there is no possibility of misselection between tools. Its purpose (reading Google Trends data for search terms) is stated explicitly and is distinct from any other exposed operation.
The single tool follows a clear verb_noun snake_case pattern (get_google_trends) that names both the action and the target service. Nothing deviates from this convention.
A one-tool surface is thin: the tool bundles summary, interest-over-time, region/metro/city breakdowns, and related queries into one overloaded call. Users cannot request a single dimension without committing to the whole bundle, and there is no companion tool for related operations (e.g. realtime trends or keyword lookup).
Coverage of the Google Trends domain is solid for a scraper: per-term summary stats, time series, geographic breakdowns at multiple granularities, and related/rising queries. Minor gaps remain, such as no realtime/trending-searches feed and no way to persist or export results.