Skip to main content
Glama

google_news_search

Retrieve news headlines, snippets, sources, and relative timestamps from Google News search results. Supports pagination, country, language, and time filters.

Instructions

Retrieves news search results from Google News (classic search-style scrape), returning headlines, snippets, source names, and relative timestamps. [Credits: 5 API credits per request] Notes: Pagination via page (0-indexed). Results returned are relative-time stamped ('19 hours ago') rather than absolute dates - use google_news_v2 for absolute dates. No id/token concepts used by this endpoint. Returns: { search_information: { query_displayed, url }, news_results: [ { title, snippet, source, lastUpdated, url, favicon } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lrNoLimit the search to one or multiple languages. Used as lang_{language_code} (e.g. lang_en). See Google LR Language Page.
tbsNoTime-Based Search filter: qdr:h (past hour), qdr:d (past 24h), qdr:w (past week), qdr:m (past month), qdr:y (past year), or a custom range.
htmlNoReturn the full HTML of the Google page instead of parsed JSON. (default: false)
nfprNoExcludes results from auto-corrected (spelling-corrected) queries. Set 1 to exclude, 0 to include. (default: 0)
pageNoPage number of Google searches. 0 = first page, 1 = second page, etc. (default: 0)
safeNoAdult content filter. Set to active to filter, or off to disable. (default: off)
uuleNoSpecifies the geographic location/locale for tailored results (e.g. w+CAIQIFJlbGF5IFN0YXRlcw==). Cannot be used with a location parameter.
queryYesGoogle Search query. Example: query=pizza
domainNoGoogle domain to get local results from a specific country, e.g. google.co.in for India, google.co.uk for the UK. See Google Domains Page. (default: google.com)
countryNoISO code of the country from which to get Google search results. See Google Country Parameter docs for full list. (default: us)
resultsNoNumber of results to scrape. Value between 1 and 100. (default: 10)
languageNoLanguage of the results, e.g. en, es, fr, de. See Google Language Page for full list. (default: en)
Behavior4/5

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

With no annotations, the description does well by disclosing credits usage, pagination behavior, relative timestamps, and that no id/token concepts are used. It could mention rate limits or error handling, but the core behavior is transparent.

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?

The description is relatively concise, combining key information in a few sentences and notes. It could be better structured (e.g., bullet points for notes), but it is efficient and front-loaded with the primary purpose.

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?

Given 12 parameters, no output schema, and no annotations, the description adequately covers the tool's purpose, behavior, and return structure (inline). It does not cover error scenarios or environment requirements, but it is sufficient for basic invocation.

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 100%, so the schema already documents all parameters. The description adds some context (e.g., pagination note, v2 reference) but does not significantly enhance parameter meaning beyond what is in the schema.

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 clearly states it retrieves news search results from Google News with specific fields (headlines, snippets, etc.). It distinguishes itself from google_news_v2 by mentioning relative timestamps vs absolute dates, and from other search tools by specifying the 'classic search-style scrape' nature.

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

Usage Guidelines4/5

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

Provides context on pagination (0-indexed), credits, and a clear alternative (google_news_v2) for absolute dates. However, it lacks explicit guidance on when to use this tool over other search tools like google_search or google_news_v2 beyond the date distinction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alessandrobenigni/ScrapingDog-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server