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

TrendPulse - Google News & Trends

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_top_news

Read-only

Fetches general Google News headlines and top stories without a keyword or topic filter to provide a broad news snapshot; use filter-specific tools when queries or locations are supplied.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
periodNoNumber of days to look back for top 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 top-story headline, publisher and 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 top-story headline, publisher and 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. Changed1 schema field changedv0.2.13
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  3. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare read-only, open-world, non-destructive behavior. The description adds that the call is unfiltered by keyword or topic seed and pulls from Google News, but it does not explain fetch behavior, defaults, or interactions among the several output-shaping parameters beyond what the schema provides.

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 short sentences, front-loaded with the core purpose and followed by the routing guidance. There is no repetition or wasted text.

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

Completeness5/5

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

With an output schema, complete parameter descriptions, and annotations covering safety, the description supplies exactly the missing selection context: this is the unfiltered top-news entry point. An agent has enough information to choose it correctly and call it with no required parameters.

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%, so the input schema already documents all five parameters. The description adds no parameter-specific guidance such as period defaults or how full_data, summarize, and headlines_only interact, so the baseline 3 is appropriate.

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 action and resource: return general headline and top-news stories from Google News without a keyword or topic seed. It immediately distinguishes this unfiltered top-news tool from the keyword, location, topic, and site news siblings.

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 a broad news snapshot and to use the keyword, location, topic, or site tools when the user supplies a filter. That is a clear when-to-use rule and a direct alternative-selection rule.

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