Skip to main content
Glama

google_news_v2

Retrieve Google News results with image URLs and accurate ISO dates. Search by query, topic token, publication token, or section token to find relevant news.

Instructions

Faster Google News endpoint (v2) that returns image URLs instead of base64 and actual ISO dates instead of relative durations. Supports browsing by topic, publication, or section tokens instead of a free-text query. [Credits: Not explicitly stated on this documentation page.] Notes: The docs reference a 'story_token' concept (used to restrict/sort story clusters via the so parameter, and excluded from combination with query/topic_token/publication_token) but do not provide a dedicated parameter entry or example for it - treat as undocumented/ambiguous and confirm with ScrapingDog support before relying on it. topic_token, publication_token, and query are mutually exclusive top-level ways to select content; section_token narrows a topic_token/publication_token further. No page/results pagination parameter is documented for this v2 endpoint. Returns: { news_results: [ { title, link, thumbnail, source, authors: [string], date (ISO 8601), rank } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
soNoSorting method: 0 = Relevance (default), 1 = Date. Can only be used with story_token. (default: 0)
queryNoA standard Google News search query; supports operators like site: or when:. Cannot be used together with publication_token, story_token, or topic_token.
countryNoTwo-letter country code for the Google search, e.g. us, uk, fr. See Google Country Parameter docs. (default: us)
languageNoLanguage of the results, e.g. en, es, fr, de. See Google Language Page. (default: en)
topic_tokenNoGoogle News topic token to get results for a particular topic (e.g. World, Business, Technology). Cannot be used with query, story_token, or publication_token.
section_tokenNoGoogle News section token to access a subsection of a specific topic (e.g. Business -> Economy). Can only be used together with topic_token or publication_token.
publication_tokenNoGoogle News publication token to get results from a specific publisher (e.g. CNN, BBC, The Guardian). Cannot be used with query, story_token, or topic_token.
Behavior5/5

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

With no annotations, the description fully discloses behavior: it returns a specific result structure, notes undocumented 'story_token' concept, warns about ambiguity, and states lack of pagination parameter. This level of transparency is exemplary for a potentially complex endpoint.

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 key information front-loaded (improvements, search modes). However, it includes a superfluous [Credits] line and the Notes section is verbose, slightly hindering conciseness.

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?

The description covers return format, parameter constraints, undocumented features, and differences from v1. It lacks explicit mention of error handling or rate limits, but given the tool's complexity, it is largely complete and helpful for an agent.

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 description coverage is 100%, but the description adds value by explaining token concepts, mutual exclusivity, and the undocumented story_token. It provides high-level context beyond the schema, justifying a score above baseline 3.

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's a faster v2 endpoint for Google News, highlighting key improvements (image URLs, ISO dates). It distinguishes from v1 and explains the different search modes (topic, publication, section tokens vs free-text query), making the purpose unambiguous.

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?

The description provides clear context on when to use this tool (v2 for faster results, image URLs, ISO dates) and explains mutual exclusivity among parameters. However, it does not explicitly compare to sibling google_news_search or state when to prefer v1, leaving some ambiguity for the agent.

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