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

TrendPulse - Google News & Trends

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_news_by_location

Read-only

Find recent Google News articles for a city, state, or country to get location-based news coverage when geography is the primary filter.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
periodNoNumber of days to look back for articles.
locationYesName of city/state/country.
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 location headlines and publisher/link metadata only. No article body, original publisher URL, or summary is fetched or inferred. meta_data marks 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 location headlines and publisher/link metadata only. No article body, original publisher URL, or summary is fetched or inferred. meta_data marks the limited RSS evidence level.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv0.2.30
    • addedInput schema / properties / location / minLength
      Added value: +1
    • addedInput schema / properties / location / 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, destructiveHint=false and openWorldHint=true, so the safety and external-dependency profile is covered. The description adds only that results are 'recent' and come from Google News; it says nothing about how the period window or summarization defaults behave. Adequate but thin beyond structured fields.

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, zero filler, and the primary purpose is front-loaded before the alternative routing. Every clause carries information an agent needs to choose the tool.

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?

With a fully described six-parameter schema and an output schema present, the description only needs to cover selection and intent, which it does. Minor omission is that it doesn't hint at the default lookback window or summarize behavior, but those are already in the schema.

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%, with each of the six parameters documented including defaults and the headlines_only evidence-level caveat. The description adds no parameter guidance of its own, so it sits at the baseline where the schema does the work.

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?

States a specific verb and resource ('Find recent Google News articles') plus the scope constraint ('about a place-focused location such as a city, state, or country'). It names the sibling get_news_by_keyword, so an agent can separate the two 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?

Explicitly gives the selection condition ('when geography is the primary filter') and routes the other case to get_news_by_keyword for 'general subject searches'. The choice between the two news tools is fully resolved by the description.

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