Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_news

Search news by query and return current results with title, source, article URL, age, and thumbnail. Refine with page, count, country, and language.

Instructions

Search Google News. Returns current Google News search results. 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

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, the description carries the full behavioral burden and does so well: it discloses the returned fields, empty-array behavior for no-results/exhausted pages, locale defaults, and a 503 error condition for blocked/malformed upstream responses. It stops short of anything like rate limits or auth requirements, but the operational disclosure is notably richer than average.

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?

Every sentence is front-loaded and load-bearing: purpose, pagination model, result fields, empty-result behavior, defaults, and error code. 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?

No output schema exists, so the description must carry return-value meaning, and it does (title, source, publisher URL, age, thumbnail). Combined with error behavior, empty results, and pagination semantics, an agent has everything needed to call and interpret this tool.

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 goes beyond the schema by clarifying the semantics of 'page' as slicing a finite result snapshot rather than traversing an index, which is interpretive value the schema's one-line description does not convey. The locale defaults restate schema content, but the paging clarification earns the bump.

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 specific verb and resource: 'Search Google News. Returns current Google News search results.' An agent immediately knows what it does. However, given a sibling named google_news_search exists in the catalog, the description does nothing to differentiate itself from that alternative.

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?

No explicit when-to-use, when-not-to-use, or named alternatives. The paging note ('Pages slice the finite result snapshot; they do not traverse the Google Search index') implies usage constraints for pagination but the agent gets no guidance on when this tool beats, say, google_news_search or duckduckgo_news.

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