Skip to main content
Glama

google: Google News results

google_news
Read-only

Google News results. News articles for a query: title, source and published time, up to about 100 items. link is Google's article link, not the publisher's URL. A failed attempt returns upstream_unavailable and is not charged. Costs 5 credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "google_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
glNoTwo-letter country code Google should bias results toward.
hlNoHost language for the results page, e.g. "en", "de". Defaults to "en".en
tbsNoTime filter: hour/day/week/month/year, as Google's own `qdr` code.
tldNoMust be "com", its default; any other value returns `invalid_request`. Use `gl` and `hl` for another country.com
uuleNoNot currently supported; any value returns `invalid_request`.
queryYesSearch query
startNo0-based result offset.
country_codeNoTwo-letter country code. Sets `gl` when `gl` is not given.
cache_max_ageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tld / description
      Previous value: -"Google marketplace TLD. One of: com, co.uk, ca, de, es, fr, it, co.jp, in, cn, com.sg, com.mx, ae, com.br, nl, com.au, com.tr, sa, se, pl. Defaults to \"com\"."New value: +"Must be \"com\", its default; any other value returns `invalid_request`. Use `gl` and `hl` for another country."
    • changedInput schema / properties / uule / description
      Previous value: -"Encoded Google location string for precise geo-targeting."New value: +"Not currently supported; any value returns `invalid_request`."
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the ~100 item ceiling, that `link` is a Google redirect rather than the publisher URL (a real gotcha for downstream fetching), that failures return `upstream_unavailable`, and that failed attempts are not charged plus a 5-credit cost. Cost and billing semantics are exactly the kind of context annotations cannot carry.

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?

Three short sentences, front-loaded with the resource and return shape, then the link caveat, then failure/cost. No filler; every clause carries information an agent would otherwise have to discover by trial.

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?

For a 9-parameter, no-output-schema tool the description covers return shape, result cap, billing and the error sentinel, which is enough to call it safely. The remaining gap is pagination: with a 0-based `start` offset and a ~100 result cap, an agent is not told whether results can be paged beyond that.

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 coverage is 89% and the schema itself documents gl, hl, tbs, tld, uule, start and country_code thoroughly, so the baseline of 3 applies. The description adds no parameter-level meaning — notably it never mentions the `start` offset for pagination or the gl/country_code fallback, both of which remain schema-only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Google News results. News articles for a query") and enumerates returned fields (title, source, published time), which implicitly separates it from the general google_search sibling. It stops short of explicitly naming google_search as the alternative for non-news web results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the word "News" — an agent can infer this is the tool for news queries rather than general web or shopping search, but there is no explicit when-to-use / when-not guidance and no named alternative. Nothing misleading, but nothing that routes the agent decisively.

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.