HasData

google_serp_news: GET /

hasdata_google_serp_news_getGoogleNews

Read-only

Get Google News Results

Retrieves Google News results by free-text query, topicToken (World, Business, Technology, etc.), sectionToken, publicationToken (e.g. CNN, BBC), or storyToken (full-coverage cluster with sort by relevance/date). Returns article title, snippet, source publisher, published date, thumbnail, and URL, plus tokens for navigating topics, sub-sections, and story clusters. Use for news monitoring, brand/PR tracking, topical aggregators, publisher-specific feeds, and drilling into full story coverage.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Free-text query as used on news.google.com. Not allowed with `topicToken`, `storyToken`, or `publicationToken`.
`gl`	No	The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`.
`hl`	No	The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`.
`so`	No	Sort order for articles in a story. Use only with storyToken.
`storyToken`	No	Token for a single news story cluster (the “Full coverage” page).
`topicToken`	No	Token for a Google News topic such as World, Business, or Technology. Not allowed with `q`, `storyToken`, or `publicationToken`.
`sectionToken`	No	Token for a sub-section under a topic, for example Business → Economy. Use only when `topicToken` or `publicationToken` is present.
`publicationToken`	No	Token for a specific publisher such as CNN or BBC. Not allowed with `q`, `storyToken`, or `topicToken`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 24, 2026

changedInput schema / properties / gl / description

Previous value: -"The two-letter country code for the country you want to limit the search to."New value: +"The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`."

removedInput schema / properties / gl / enum

Removed value: -[
-  "ac",
-  "af",
-  "al",
-  "dz",
-  "as",
-  "ad",
-  "ao",
-  "ai",
-  "aq",
-  "ag",
-  "ar",
-  "am",
-  "aw",
-  "au",
-  "at",
-  "az",
-  "bs",
-  "bh",
-  "bd",
-  "bb",
-  "by",
-  "be",
-  "bz",
-  "bj",
-  "bm",
-  "bt",
-  "bo",
-  "ba",
-  "bw",
-  "bv",
-  "br",
-  "io",
-  "bn",
-  "bg",
-  "bf",
-  "bi",
-  "kh",
-  "cm",
-  "ca",
-  "cv",
-  "ky",
-  "cf",
-  "td",
-  "cl",
-  "cn",
-  "cx",
-  "cc",
-  "co",
-  "km",
-  "cg",
-  "cd",
-  "ck",
-  "cr",
-  "ci",
-  "hr",
-  "cu",
-  "cy",
-  "cz",
-  "dk",
-  "dj",
-  "dm",
-  "do",
-  "ec",
-  "eg",
-  "sv",
-  "gq",
-  "er",
-  "ee",
-  "et",
-  "fk",
-  "fo",
-  "fj",
-  "fi",
-  "fr",
-  "gf",
-  "pf",
-  "tf",
-  "ga",
-  "gm",
-  "ge",
-  "de",
-  "gg",
-  "gh",
-  "gi",
-  "gr",
-  "gl",
-  "gd",
-  "gp",
-  "gu",
-  "gt",
-  "gn",
-  "gw",
-  "gy",
-  "ht",
-  "hm",
-  "va",
-  "hn",
-  "hk",
-  "hu",
-  "im",
-  "is",
-  "in",
-  "id",
-  "ir",
-  "iq",
-  "ie",
-  "il",
-  "it",
-  "je",
-  "jm",
-  "jp",
-  "jo",
-  "kz",
-  "ke",
-  "ki",
-  "kp",
-  "kr",
-  "kw",
-  "kg",
-  "la",
-  "lv",
-  "lb",
-  "ls",
-  "lr",
-  "ly",
-  "li",
-  "lt",
-  "lu",
-  "me",
-  "mo",
-  "mk",
-  "mg",
-  "mw",
-  "my",
-  "mv",
-  "ml",
-  "mt",
-  "mh",
-  "mq",
-  "mr",
-  "mu",
-  "yt",
-  "mx",
-  "fm",
-  "md",
-  "mc",
-  "mn",
-  "ms",
-  "ma",
-  "mz",
-  "mm",
-  "na",
-  "nr",
-  "np",
-  "nl",
-  "an",
-  "nc",
-  "nz",
-  "ni",
-  "ne",
-  "ng",
-  "nu",
-  "nf",
-  "mp",
-  "no",
-  "om",
-  "pk",
-  "pw",
-  "ps",
-  "pa",
-  "pg",
-  "py",
-  "pe",
-  "ph",
-  "pn",
-  "pl",
-  "pt",
-  "pr",
-  "qa",
-  "re",
-  "ro",
-  "ru",
-  "rw",
-  "sh",
-  "kn",
-  "lc",
-  "pm",
-  "vc",
-  "ws",
-  "sm",
-  "st",
-  "sa",
-  "sn",
-  "rs",
-  "sc",
-  "sl",
-  "sg",
-  "sk",
-  "si",
-  "sb",
-  "so",
-  "za",
-  "gs",
-  "es",
-  "lk",
-  "sd",
-  "sr",
-  "sj",
-  "sz",
-  "se",
-  "ch",
-  "sy",
-  "tw",
-  "tj",
-  "tz",
-  "th",
-  "tl",
-  "tg",
-  "tk",
-  "to",
-  "tt",
-  "tn",
-  "tr",
-  "tm",
-  "tc",
-  "tv",
-  "ug",
-  "ua",
-  "ae",
-  "uk",
-  "gb",
-  "us",
-  "um",
-  "uy",
-  "uz",
-  "vu",
-  "ve",
-  "vn",
-  "vg",
-  "vi",
-  "wf",
-  "eh",
-  "ye",
-  "zm",
-  "zw"
-]

changedInput schema / properties / hl / description

Previous value: -"The two-letter language code for the language you want to use for the search."New value: +"The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`."

removedInput schema / properties / hl / enum

Removed value: -[
-  "af",
-  "ak",
-  "sq",
-  "ws",
-  "am",
-  "ar",
-  "hy",
-  "az",
-  "eu",
-  "be",
-  "bem",
-  "bn",
-  "bh",
-  "xx-bork",
-  "bs",
-  "br",
-  "bg",
-  "bt",
-  "km",
-  "ca",
-  "chr",
-  "ny",
-  "zh-cn",
-  "zh-tw",
-  "zh-hk",
-  "co",
-  "hr",
-  "cs",
-  "da",
-  "nl",
-  "xx-elmer",
-  "en",
-  "eo",
-  "et",
-  "ee",
-  "fo",
-  "tl",
-  "fil",
-  "fi",
-  "fr",
-  "fy",
-  "gaa",
-  "gl",
-  "ka",
-  "de",
-  "el",
-  "kl",
-  "gn",
-  "gu",
-  "xx-hacker",
-  "ht",
-  "ha",
-  "haw",
-  "iw",
-  "he",
-  "hi",
-  "hu",
-  "is",
-  "ig",
-  "id",
-  "ia",
-  "ga",
-  "it",
-  "ja",
-  "jw",
-  "kn",
-  "kk",
-  "rw",
-  "rn",
-  "xx-klingon",
-  "kg",
-  "ko",
-  "kri",
-  "ku",
-  "ckb",
-  "ky",
-  "lo",
-  "la",
-  "lv",
-  "ln",
-  "lt",
-  "loz",
-  "lg",
-  "ach",
-  "mk",
-  "mg",
-  "my",
-  "ml",
-  "mt",
-  "mv",
-  "mi",
-  "mr",
-  "mfe",
-  "mo",
-  "mn",
-  "ms",
-  "sr-me",
-  "ne",
-  "pcm",
-  "nso",
-  "no",
-  "nn",
-  "oc",
-  "or",
-  "om",
-  "ps",
-  "fa",
-  "xx-pirate",
-  "pl",
-  "pt",
-  "pt-br",
-  "pt-pt",
-  "pa",
-  "qu",
-  "ro",
-  "rm",
-  "nyn",
-  "ru",
-  "gd",
-  "sr",
-  "sh",
-  "st",
-  "tn",
-  "crs",
-  "sn",
-  "sd",
-  "si",
-  "sk",
-  "sl",
-  "so",
-  "es",
-  "es-419",
-  "su",
-  "sw",
-  "sv",
-  "tg",
-  "ta",
-  "tt",
-  "te",
-  "th",
-  "ti",
-  "to",
-  "lua",
-  "tum",
-  "tr",
-  "tk",
-  "tw",
-  "ug",
-  "uk",
-  "ur",
-  "uz",
-  "vu",
-  "vi",
-  "cy",
-  "wo",
-  "xh",
-  "yi",
-  "yo",
-  "zu"
-]

First observedApr 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the return payload (title, snippet, source, published date, thumbnail, URL, navigation tokens) and the token-based mode switching, which annotations do not convey. It omits rate limits, pagination, and auth requirements.

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?

Well front-loaded: the lead line names the resource before the retrieval-mode detail, and the use-case sentence is placed last. It is dense but each sentence (modes, return fields, use cases) carries distinct information; only the redundant opening echo of the name is mild waste.

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?

For an 8-parameter read tool with no output schema, the description covers the retrieval modes, the mutual-exclusion constraints among tokens, and the return contents, which is enough for an agent to invoke it correctly. Missing only secondary operational detail such as pagination or result limits, which is acceptable given rich schema coverage and safety annotations.

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%, so baseline is 3; the description adds a mode-selection framing by grouping the tokens into named retrieval strategies and clarifying that storyToken is a 'full-coverage cluster with sort by relevance/date' (explaining the so parameter's purpose). It repeats several schema examples rather than supplying new syntax, so it only modestly exceeds baseline.

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 ('Retrieves') and resource ('Google News results') and enumerates the five retrieval modes (free-text query, topicToken, sectionToken, publicationToken, storyToken), making the scope concrete. However, it never names or contrasts with siblings like serp_getSearchResults for non-news web results, so an agent must infer the news-only boundary from the tool name.

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?

Explicitly lists use cases ('news monitoring, brand/PR tracking, topical aggregators, publisher-specific feeds, and drilling into full story coverage'), giving clear triggering context. It stops short of when-NOT-to-use or naming an alternative sibling (e.g. general SERP search), so it does not reach the 5 bar.

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

All HasData tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?