Skip to main content
Glama

Google News Search

google_news_search
Read-only

A find-companies News-mode discovery source, used alongside search_news_events, tavily_search, and exa_search_news — the News-mode skill owns the routing (which signals fan out here). Its edge is Google's local and trade-press index: hyper-local expansion stories, plant incidents within hours of publication, and small-market executive moves the other sources' indexes miss. Returns raw articles, not company rows — extract the company from each article's title/snippet the same way as tavily_search results.

Compose KEYWORD-style queries — the terms a journalist's headline would contain, e.g. 'appoints new chief marketing officer' or 'breaks ground manufacturing facility'. Google matches keywords, not meaning: full-sentence semantic phrasing ("A company that recently...") returns ZERO results. Geographic scoping via keywords is brittle (a location term matches any article containing the word, wherever the company is) — prefer scoping by event keywords and filtering location downstream. One query per signal, all in one call (the tool fans them out in parallel; one tool call is one LLM round).

Expect the same story to arrive several times from different outlets — Google clusters dilute a page's effective yield to ~5–7 distinct companies. Dedup is on exact URL here; cross-outlet same-story dedup happens downstream at record_search_results.

Articles are recency-bounded server-side by Google's coarse day/week/month/year buckets, using the smallest bucket covering lookback_days (default 30) — a bucket can exceed the window, so also check each row's published_at when the window matters. A news scan passes the window from its trigger prompt.

Costs 0.05 Sliq credits per query that returns without error; a failed query is free. Companies you record from its articles are not charged. Soft-fails on insufficient credits: the charge is capped at the remaining balance. Dict with articles array and count. Each article row is {title, url, source, snippet, date, published_at, query} — source is the publisher name, date is Google's relative publish string ("2 days ago"), published_at is a coarse UTC ISO estimate derived from it (None when unparseable), and query names the originating query. Rows are deduped by URL across queries.

If every query failed with an upstream error and nothing landed, also google_news_available: False plus a human-readable error — a source outage, NOT a genuinely empty feed. Partial failure (some queries errored, others returned) stays silent and reports only the articles.

On insufficient Sliq credits the call is refused before running — it raises InsufficientCreditsError instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queriesYesOne keyword-style news query per signal. Pass a list of one for a single-signal lookup.
lookback_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only provide readOnlyHint=true, yet the description discloses pricing (0.05 credits per successful query, free on failure), insufficient-credit soft-fail behavior, URL-only dedup with downstream same-story dedup, recency-bucket semantics, and partial-failure silence — all behavioral traits beyond annotations.

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

Conciseness4/5

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

Front-loaded with purpose and routing, then query-composition, dedup, cost, and return shape. Dense but nearly every sentence carries operative detail; could be trimmed slightly but largely earns its length.

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?

For a 2-param tool with no output schema, the description covers query construction, geographic-scoping caveat, dedup, cost, and the exact return shape plus error/partial-failure states — everything needed to call and interpret results correctly.

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

Parameters4/5

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

With 50% schema coverage, the description compensates by explaining how to compose 'queries' (one per signal, fanned out in parallel) and the semantics of 'lookback_days' (default 30, mapped to Google's coarse buckets, may exceed the window). It adds real meaning beyond the schema's bare 'keyword-style query per signal' note.

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+resource+mechanism ('Discover companies from recent news via Google News keyword search') and names the sibling discovery sources it sits alongside (search_news_events, tavily_search, exa_search_news), clarifying its niche (local/trade-press index) versus theirs.

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 states when to use it, how the News-mode skill routes signals to it, and when to prefer other sources. Adds strong query-composition guidance ('keyword style, not semantic phrasing') and warns against geographic scoping in favor of event keywords with downstream filtering.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources