Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_news_search

Search current news articles by keyword, language, and country, returning structured JSON results with pagination for paged result snapshots.

Instructions

Search Google News with JSON. Restored JSON compatibility endpoint. Returns current Google News articles. Pages slice the finite current result snapshot. Uses the legacy result array and field names; no-results searches and exhausted pages return an empty result array.

Input Schema

NameRequiredDescriptionDefault
searchOptionYesSearch options; keyword, language and country are required. limit defaults to 10 and is clamped to 10..100; page defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains that results come from a finite snapshot, pages slice that snapshot, and no-results or exhausted pages return an empty array. It also notes legacy result array/field names, which is useful context. Missing auth or rate-limit details, but those are less critical for a read-only search.

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?

Four sentences, reasonably front-loaded with the core action first. Some redundancy ("with JSON" / "Restored JSON compatibility endpoint") but no significant wasted space.

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?

No output schema exists, so the description must explain return values, and it does (current articles, legacy array, empty array on no results/exhausted pages). It is adequate for a single-parameter search tool, though it could explicitly contrast with google_news.

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 100%, so the baseline is 3. The description adds only a behavioral note about pagination ("pages slice the finite current result snapshot") but gives no extra meaning for keyword, country, or language.

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 clear verb and resource ("Search Google News") and notes it returns current articles. It doesn't differentiate from the sibling google_news tool, and the phrase "with JSON / Restored JSON compatibility endpoint" is unexplained boilerplate.

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?

No guidance on when to use this versus alternatives like google_news, bing_news, or yahoo_search_news. It gives behavioral notes (pagination, empty results) but never routes the agent to the right tool.

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

Deploy Server

Other Tools