Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_news

Search Google News by query and return structured results with title, source, article URL, age, and thumbnail, with country and language options.

Instructions

Search Google News. Returns current Google News search results using anonymous HTTP requests with fresh proxy profiles, without browser rendering. Pages slice the finite result snapshot; they do not traverse the Google Search index. Results include title, source, publisher article URL, age, and thumbnail when available. Valid no-results searches and exhausted pages return an empty array. Locale defaults to country=us and lang=en. Returns 503 for blocked or malformed upstream responses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query
langNoGoogle UI language; defaults to en
pageNo1-based page within the current finite result snapshot; defaults to 1
countNoResults per page; defaults to 10, clamped to 1..50
countryNoTwo-letter country code; defaults to us

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • changedInput schema / properties / page / description
      Previous value: -"1-based page number; defaults to 1"New value: +"1-based page within the current finite result snapshot; defaults to 1"
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently explains the anonymous request mechanism, no browser rendering, finite snapshot pagination, result fields, empty array behavior, locale defaults, and 503 error on blocked/malformed responses. This is substantial coverage, though it does not explicitly state read-only semantics or rate limits, which are minor given the tool's nature.

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?

The description is information-dense yet well-structured. It leads with the primary action, then systematically covers mechanism, pagination behavior, result fields, edge cases, defaults, and error handling. Every sentence adds value; there is no filler or redundancy.

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?

For a search tool with 5 parameters, no output schema, and no annotations, the description covers all essential aspects: what results contain, how pagination works, default locale, empty-array behavior, and error handling. Nothing critical is missing for an agent to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema: it clarifies that page slices a finite snapshot, that exhausted pages return an empty array, and it reinforces the locale defaults. This helps an agent understand the pagination model and defaults, going beyond the simple parameter descriptions.

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 clearly states the tool searches Google News and returns search results, using specific implementation details (anonymous HTTP, fresh proxies, no browser rendering). It is specific about the resource and action. However, it does not differentiate from the sibling tool google_news_search, which also appears in the sibling list, so it misses the explicit sibling distinction that would earn a 5.

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?

The description gives useful behavioral context (pagination, locale defaults, empty array on no results) but provides no explicit guidance on when to choose this tool over alternatives like google_news_search. There is no when/when-not guidance, only implied usage for general Google News searches.

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