Skip to main content
Glama
Sign In
TrendPulse - Google News & Trends

TrendPulse - Google News & Trends

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_news_by_topic

Read-only

Fetch recent Google News articles for a predefined topic category such as BUSINESS, TECHNOLOGY, or SPORTS, with optional lookback days, result limits, and summaries for category browsing.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
topicYesTopic to search for articles.
periodNoNumber of days to look back for articles.
full_dataNoReturn full data for each article. If False a summary should be created by setting the summarize flag
summarizeNoGenerate a summary of the article, will first try LLM Sampling but if unavailable will use nlp
max_resultsNoMaximum number of results to return.
headlines_onlyNoReturn dated Google News RSS topic headlines and publisher/link metadata only. No article body, original publisher URL, or summary is fetched or inferred. meta_data identifies the limited RSS evidence level.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.46
    • addedInput schema / properties / headlines_only
      Added value: +{
+  "default": false,
+  "description": "Return dated Google News RSS topic headlines and publisher/link metadata only. No article body, original publisher URL, or summary is fetched or inferred. meta_data identifies the limited RSS evidence level.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv0.2.30
    • addedInput schema / properties / topic / minLength
      Added value: +1
    • addedInput schema / properties / topic / pattern
      Added value: +".*\\S.*"
  3. Changed1 schema field changedv0.2.13
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  4. First observed

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds 'recent' and category scope, but does not disclose article-fetching details beyond what annotations and the output schema provide, making 3 appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences are front-loaded with purpose followed by usage guidance and the named alternative. There is no wasted text or restatement of the tool name, and every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with an output schema, the description covers purpose and sibling routing while the schema handles parameter details. The main gap is that the 'predefined' topic categories are only exemplified, not enumerated, although the get_categories sibling may help; overall the definition is mostly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema itself documents all six parameters including defaults and meanings of period, full_data, summarize, max_results, and headlines_only. The description only illustrates topic with category examples and adds no parameter syntax or constraints beyond the schema, so baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Find') and resource ('recent Google News articles') with clear scope ('from a predefined Google News topic category'). It explicitly distinguishes this tool from get_news_by_keyword, so an agent can tell topic browsing apart from keyword search without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this for topic category browsing such as BUSINESS, TECHNOLOGY, or SPORTS, and directs free-form queries to get_news_by_keyword. This gives both a when-to-use condition and a named alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools