TrendPulse - Google News & Trends
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PROXY | No | Proxy URL for HTTP requests. | |
| HTTPS_PROXY | No | Proxy URL for HTTPS requests. | |
| GOOGLE_TRENDS_DELAY | No | Delay between Google Trends requests to avoid rate limits. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_news_by_keywordA | Find recent Google News articles for a free-form keyword or phrase. Use this for ad-hoc subject searches; use get_news_by_topic for a predefined topic category or get_news_by_site for one publisher. |
| get_news_by_locationA | Find recent Google News articles about a place-focused location such as a city, state, or country. Use this when geography is the primary filter; use get_news_by_keyword for general subject searches. |
| get_news_by_topicA | Find recent Google News articles from a predefined Google News topic category. Use this for topic category browsing such as BUSINESS, TECHNOLOGY, or SPORTS; use get_news_by_keyword for a free-form query. |
| get_top_newsA | Return general headline and top-news stories from Google News without a keyword or topic seed. Use this for a broad news snapshot; use the keyword, location, topic, or site tools when the user gives a filter. |
| get_trending_termsA | Return terms that are trending now for a geography, optionally with related news metadata. Use this for current trend discovery; use get_trends when the user wants historical interest over time for known keywords. |
| get_trendsA | Return historical Google Trends interest-over-time points for one or more known keywords. Use this for trajectory and comparisons across a timeframe; values are normalized 0-100 interest scores, not absolute search volume. Use get_trending_terms for what is trending now. |
| get_growthA | Estimate momentum for one or more known keywords across requested growth windows. Use this when percentage growth is the goal; use get_trends when the user needs the underlying historical time series. |
| get_ranked_trendsA | Return currently trending keywords ranked by week-over-week growth or volume. Use this when explicit ranked order matters; use get_top_trends for a simpler current feed and get_trends for historical series. |
| get_top_trendsA | Return a bounded current topic discovery feed from Google Trends RSS, including related news where available. Use this for current top or daily trends; use get_ranked_trends when explicit ranking by growth or volume matters. |
| get_news_by_siteA | Find recent Google News articles from one publisher domain. Use this when the user wants source-specific coverage; use get_news_by_keyword for cross-publisher subject search. |
| get_article_contentA | Download and parse one specific news article when you already have an article URL. Use it to retrieve article text or metadata or summarize that URL; do not use it for discovery - use the news search tools instead. |
| get_interest_by_regionA | Return geographic Google Trends interest for one or more known keywords at country, region, city, or DMA resolution. Use this to compare where demand is strongest; use get_trends for interest over time instead. |
| get_related_queriesA | Return top and rising literal search queries related to one seed keyword. Use this for query expansion; use get_related_topics for topic entities or get_suggestions for autocomplete candidates. |
| get_related_topicsA | Return top and rising Google Trends topic entities related to one seed keyword. Use this for entity or topic expansion; use get_related_queries for literal search queries. |
| get_suggestionsA | Return Google Trends autocomplete suggestions for a seed keyword. Use this for lightweight autocomplete or entity candidates; use get_related_queries when you need top or rising demand signals. |
| get_categoriesA | Return a bounded page of Google Trends category IDs and names for use in the cat parameter of trend tools. Use query to find categories by name and offset/limit to page through broader results; do not guess category IDs. |
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 16 tools
Most tools have clear axes of distinction (news vs. trends, and filter-by-keyword/location/topic/site), and the descriptions cross-reference each other explicitly. However, three tools — get_trending_terms, get_top_trends, and get_ranked_trends — all return a current trending feed with only subtle differences, which is a likely source of misselection. get_growth vs. get_trends is also a thin boundary (derived metric vs. underlying series).
Every tool follows a consistent get_<noun_phrase> snake_case pattern, which is easy to scan and predict. The minor inconsistency is noun choice for near-identical concepts (terms vs. trends vs. top_trends vs. ranked_trends), which slightly obscures semantics rather than breaking the pattern.
16 tools is slightly heavy but reasonable for a two-domain server (news search + trends analytics). Each tool covers a distinct retrieval dimension (source filter, geography, time series, region, growth) rather than duplicating surface area. No obviously redundant slot beyond the trending-feed trio.
The surface covers trend discovery, historical series, related queries/topics, suggestions, categories, regional interest, growth, and ranking, plus news by keyword/location/topic/site, top news, and full article retrieval. Minor gaps exist: no explicit publisher/source listing tool and no combined news+trend workflow, but agents can work around these with the provided filters.