Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

google_news

Read-onlyIdempotent

Retrieve structured Google News articles for any query. Supports filtering by country, language, date range, and time period.

Instructions

Retrieve parsed Google News results for a query.

    Returns structured news articles (title, source, link, timestamp, snippet)
    for a query from Google News.

    When to use:
    - Monitoring news coverage or headlines for a topic, brand, or entity
    - Time-bounded news scans (last hour/day/week or a custom date range)

    When NOT to use:
    - General web results (use 'google_search')
    - Reading the full text of a specific article (use 'scrape' on its URL)

    Args:
        params (GoogleNewsParams): query (required) plus optional localization,
            pagination, date filters (date_range_start/end, time_period), tld,
            and output_format.

    Returns:
        str: JSON (default) or CSV containing the structured news results.

    Raises:
        ToolError: If the API key is missing, the rate limit is exceeded, or
            the request fails.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false. The description adds behavioral context: returns structured news, raises ToolError on API/rate-limit issues. No contradictions. Adds value 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?

The description is well-structured with sections (when to use, args, returns, raises) and front-loads purpose. A bit verbose but acceptable; every section earns its place.

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?

Given the moderate complexity (many parameters, output schema exists), the description covers purpose, usage, parameters, return format (JSON/CSV), and error conditions. Output schema covers return values, so description is complete.

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 high (each parameter in GoogleNewsParams has a description). The tool description summarizes parameters briefly but does not add significant new meaning. Baseline 3 is appropriate.

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 'Retrieve parsed Google News results for a query' and specifies the returned fields (title, source, link, timestamp, snippet). It distinguishes from sibling tools like 'google_search' and 'scrape'.

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?

The description explicitly lists when to use (monitoring news, time-bounded scans) and when NOT to use (general web, reading full articles) with alternatives named. This provides excellent guidance.

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/scraperapi/scraperapi-mcp'

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