google-data-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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_trends_interestA | Google Trends interest over time for ONE keyword. Values are 0-100 relative WITHIN this single request, so they are not comparable to another call's numbers — use google_trends_compare when you need to rank terms against each other. |
| google_trends_compareA | Compare up to 5 keywords in ONE Google Trends request, so their 0-100 values ARE normalised against each other and can be ranked. Google silently drops a 6th term, so 6+ is refused rather than answered with a term missing. |
| google_trends_trendingB | What is trending on Google right now in one country. |
| youtube_listingA | List videos from YouTube: a channel's Shorts tab, a channel's videos tab, or search results. Returns videoId, title, view count, and (for videos/search) a publish date. Transcripts are NOT available from this server — Google gates them behind a token this server cannot mint. |
| google_ads_advertisersA | Find advertisers in Google's Ads Transparency Center by name. Returns each advertiser's id, country and Google's declared ad count — pass the id to google_ads_creatives. |
| google_ads_creativesA | Every ad an advertiser is currently running, from Google's Ads Transparency Center: creative id, format, preview URL and first/last shown dates. An advertiser with zero ads is a real answer — Google keeps advertisers whose ads have stopped running. |
| google_play_reviewsA | Reviews for an Android app: rating, text, date, app version, thumbs-up and the developer's reply. Reviewer names and avatars are omitted unless you ask for them. Note each language/country returns a DIFFERENT set of reviews, so vary hl/gl to widen coverage. |
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 7 tools
Each tool targets a distinct Google service or distinct operation within a service. google_trends_compare and google_trends_interest are clearly differentiated by their normalization semantics, and the ad tools (advertisers vs creatives) have distinct purposes. No two tools could be easily confused.
Tool names follow a consistent service-prefix pattern (google_trends_, google_ads_, youtube_, google_play_), but the second part mixes nouns, verbs, and gerunds (e.g., compare, trending, listing, advertisers, creatives, reviews). While not perfectly uniform, the pattern is predictable and readable.
With 7 tools, the set is well-scoped. It covers multiple Google data services without bloating, and each tool addresses a common use case, making the count feel right for the stated purpose.
The tool surface covers core workflows for Trends (compare, trending, interest), Ads (advertiser search and creatives), YouTube (listing videos), and Play (reviews). Minor gaps exist (e.g., no YouTube channel details, no Play app metadata), but the essential read operations are present. The server explicitly notes limitations like no transcripts, which clarifies its boundaries.