Skip to main content
Glama

CrawlerData: Google Shopping & SERP

Google News

google_news
Read-only

Google News results: headline, source, date, snippet and link. 1 credit.

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
latNoSearch from a point: its latitude in degrees, e.g. 40.7580. Give lat and lng together, instead of location or uule; set country to the point's country (default "us").
lngNoSearch from a point: its longitude in degrees, e.g. -73.9855. Give lat and lng together.
pageNo
uuleNoAdvanced: a raw Google uule value ("w+...", "a+...", "j+..."), plain or URL-encoded as copied from a Google URL. Use location instead unless you already have uule values.
queryYes
countryNoTwo-letter country code. Defaults to "us", or to the country of location.
languageNoen
locationNoSearch from a city, region or postal code: a Google canonical location name, "City,Region,Country" (Google Ads geotarget format), e.g. "Austin,Texas,United States". When country is omitted it is taken from the location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / lat
      Added value: +{
      +  "description": "Search from a point: its latitude in degrees, e.g. 40.7580. Give lat and lng together, instead of location or uule; set country to the point's country (default \"us\").",
      +  "maximum": 90,
      +  "minimum": -90,
      +  "type": "number"
      +}
    • addedInput schema / properties / lng
      Added value: +{
      +  "description": "Search from a point: its longitude in degrees, e.g. -73.9855. Give lat and lng together.",
      +  "maximum": 180,
      +  "minimum": -180,
      +  "type": "number"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / uule / description
      Previous value: -"Advanced: a raw Google uule value (\"w+...\", \"a+...\", \"j+...\"), sent as is. Use location instead unless you already have uule values."New value: +"Advanced: a raw Google uule value (\"w+...\", \"a+...\", \"j+...\"), plain or URL-encoded as copied from a Google URL. Use location instead unless you already have uule values."
    • removedInput schema / properties / uule / pattern
      Removed value: -"^[A-Za-z][+ ][A-Za-z0-9+/_=-]{4,1000}$"
  3. Changed2 schema fields changed
    • changedInput schema / properties / uule / description
      Previous value: -"Advanced: a raw Google uule value, sent as is. Use location instead unless you already have uule values."New value: +"Advanced: a raw Google uule value (\"w+...\", \"a+...\", \"j+...\"), sent as is. Use location instead unless you already have uule values."
    • changedInput schema / properties / uule / pattern
      Previous value: -"^[aw][+ ][A-Za-z0-9+/_=-]{4,1000}$"New value: +"^[A-Za-z][+ ][A-Za-z0-9+/_=-]{4,1000}$"
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-web behavior are covered structurally. The description adds genuinely new context by listing the returned fields and disclosing the '1 credit' cost, which matters for budget-aware agents, but it says nothing about the page cap (1-10), result counts per page, or geotargeting precedence.

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?

A single tight sentence front-loads the resource and then the payload, with zero filler. It is efficient, though the extreme brevity is bordering on under-specification rather than pure concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, enumerating the returned fields is the right move and partly fills the gap. However, an 8-parameter search tool with three competing geo-addressing modes (location, lat/lng, uule) and a 10-page cap deserves at least a note on pagination and geo precedence, which the description omits entirely.

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 sits at 63%, above the high-coverage threshold, so the schema largely documents lat/lng, uule, location, and country itself. The description contributes no parameter meaning at all — not even clarifying that 'query' is the news search string — so it neither adds value nor compensates for the undocumented page/language/query fields.

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?

The description names the resource ('Google News results') and enumerates the returned fields (headline, source, date, snippet, link), so an agent knows exactly what this call yields. The verb is only implied via 'results', and it never explicitly contrasts itself with google_search as the non-news alternative, leaving sibling differentiation to the name alone.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance anywhere in the text. Nothing tells an agent to prefer google_news over google_search for current events, or how the geo parameters should be chosen, so selection must be inferred entirely from the tool name.

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