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

TrendPulse - Google News & Trends

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_news_by_site

Read-only

Find recent Google News articles from a specified publisher domain to get source-specific coverage. Use it when you need news from one site rather than cross-publisher search.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
siteYesDomain of the news site, e.g. 'cnn.com'.
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 publisher-site 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 publisher-site 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 / site / minLength
      Added value: +1
    • addedInput schema / properties / site / 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 and network profile is known. The description adds only the 'recent' recency framing; it says nothing about the interaction between full_data, summarize and headlines_only, nor about LLM-sampling fallback behavior, which is the operationally risky part of this tool.

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, no filler, with the tool's identity front-loaded and the disambiguation clause second. Every clause 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?

With an output schema, full parameter documentation, and read-only annotations, the description need not explain return values. It is complete for selection; the only gap is silence on how the summarize/full_data/headlines_only flags trade off, which is the main way an agent could misconfigure this call.

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 every parameter, including the nuanced headlines_only evidence-level note, is documented in the schema. The description contributes no parameter-level meaning beyond what is already structured, 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?

The description states a specific verb and resource ('Find recent Google News articles') plus the scope ('from one publisher domain'), which is exactly what distinguishes it from keyword/location/topic siblings. An agent can select it without opening the 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 gives an explicit when-to-use condition ('user wants source-specific coverage') and names the alternative tool (get_news_by_keyword) with the condition that selects it. Routing between the two news-search siblings is fully determined.

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