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

TrendPulse - Google News & Trends

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_news_by_keyword

Read-only

Search Google News by keyword to find recent articles on any topic, with optional summaries or headlines for ad-hoc research.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
periodNoNumber of days to look back for articles.
keywordYesSearch term to find 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 only dated Google News RSS title, publisher, and link metadata. No original publisher URL, full article text, or summary is fetched or inferred. The url field is a Google News RSS link; meta_data marks its limited 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 only dated Google News RSS title, publisher, and link metadata. No original publisher URL, full article text, or summary is fetched or inferred. The url field is a Google News RSS link; meta_data marks its limited evidence level.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv0.2.30
    • addedInput schema / properties / keyword / minLength
      Added value: +1
    • addedInput schema / properties / keyword / 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 open-web profile is covered structurally. The description adds only the recency framing ('recent') and nothing about the LLM-sampling summarization path, result caps, or failure modes — those live solely in the schema.

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 waste: the capability comes first, the disambiguation second. Nothing is repeated from the schema.

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?

An output schema exists and the parameter schema is fully described, so return values and flags need not be explained here. The description covers what and when; it only leaves implicit why one would prefer this over the unmentioned siblings such as get_news_by_location or get_top_news.

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 every parameter (period, keyword, full_data, summarize, max_results, headlines_only) is already documented in the input schema, including the sampling/nlp fallback and the headlines-only evidence caveat. The description adds no parameter meaning beyond restating that the keyword is free-form, so the baseline 3 applies.

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 accepted input shape ('free-form keyword or phrase'). It also names the two nearest siblings it is not, so an agent can distinguish it without opening any 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?

Gives an explicit routing rule: use this for ad-hoc subject searches, use get_news_by_topic for a predefined category, get_news_by_site for one publisher. The condition that selects each alternative is stated, not inferred.

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