Skip to main content
Glama

Search News

search_news
Read-onlyIdempotent

Searches Google News and returns up to 20 articles (title, url, source, published_at, snippet), localized by country and language. published_at is the source's own text and can be relative, such as "2 hours ago". It does not return article bodies (use scrape_url on an article url) and is not general web search (use google_search). A search with no matches is charged; errors are not. Required: query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based results page, integer from 0: 0 is the first page, 1 the second, e.g. 1. Omit for the first page; each page is a separate charged call.
queryYesNews search text, 1-500 characters, e.g. "renewable energy policy".
countryNoTwo-letter country code that localizes the news, e.g. "it" or "gb". Omit for the source default, us.
resultsNoMaximum articles returned, integer 1-20, default 10, e.g. 5.
languageNoTwo-letter language code for the articles, e.g. "en" or "it". Omit for the source default, en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter country code used to localize news results."New value: +"Two-letter country code that localizes the news, e.g. \"it\" or \"gb\". Omit for the source default, us."
    • changedInput schema / properties / language / description
      Previous value: -"Two-letter language code for news result text."New value: +"Two-letter language code for the articles, e.g. \"en\" or \"it\". Omit for the source default, en."
    • changedInput schema / properties / page / description
      Previous value: -"Zero-based news result page number."New value: +"Zero-based results page, integer from 0: 0 is the first page, 1 the second, e.g. 1. Omit for the first page; each page is a separate charged call."
    • changedInput schema / properties / query / description
      Previous value: -"News search query."New value: +"News search text, 1-500 characters, e.g. \"renewable energy policy\"."
    • changedInput schema / properties / results / description
      Previous value: -"Maximum number of news articles to return."New value: +"Maximum articles returned, integer 1-20, default 10, e.g. 5."
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so safety and idempotency are covered structurally. The description still earns credit for disclosing the billing model (no-match searches are charged, errors are not) and warning that published_at may be relative source text. That is real added context, though it stops short of describing ranking, rate limits, or ordering guarantees.

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?

Four sentences, front-loaded with the capability and return fields, then exclusions, then cost semantics. Every sentence carries distinct information with no restatement of the title.

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?

With no output schema, the description compensates by listing the returned fields, and it covers the two agent-critical unknowns for a paid external search: billing behavior and the non-absolute nature of published_at. Combined with a fully documented 5-parameter schema, nothing needed to call it correctly is missing.

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 coverage is 100%, and each parameter already carries examples, enum ranges, and defaults, so the baseline is 3. The description only restates localization by country/language and that query is required, adding no syntax or constraint detail beyond the schema itself.

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?

States a specific verb and resource ('Searches Google News'), enumerates the returned fields, caps scope at 20 articles, and notes localization. It explicitly names what it is not (article bodies, general web search), which separates it from google_search and scrape_url in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use scrape_url on an article url for full bodies, use google_search for general web search. It also states the one required parameter, so an agent knows the minimum viable call without opening the schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources