Skip to main content
Glama

NewzAI News MCP server

get_related_news

Read-only

Fetches news related to a given topic or a specific news item. Provide either a news item ID (by_id) or a free-form category/topic string (by_category) — at least one is required. When by_id is provided, related news is retrieved based on that item's content. Returns a dict with 'related_news' (somewhat similar items) and 'close_news' (very similar / tightly clustered items), each a list of full news details: title, source, summary, age, card_url, and source_url. Login is required to access this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
by_idNoID of a specific news item to find related news for
top_kNoMaximum number of related news items to return
regionYesRequired region filter for the related news (e.g., 'india', 'united-states'). If missing from the user's request, ask the user which region/country they want.
languageNoOutput language code for the related news (e.g., 'en' for English)en
by_categoryNoFree-form topic or category string (e.g., 'climate change', 'AI chips')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
close_newsYes
related_newsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / region / enum
      Added value: +[
      +  "india",
      +  "united-states",
      +  "united-kingdom",
      +  "japan",
      +  "international"
      +]
  2. Changed3 schema fields changed
    • removedInput schema / properties / region / default
      Removed value: -"india"
    • changedInput schema / properties / region / description
      Previous value: -"Region filter for the related news (e.g., 'india', 'united-states')"New value: +"Required region filter for the related news (e.g., 'india', 'united-states'). If missing from the user's request, ask the user which region/country they want."
    • addedInput schema / required
      Added value: +[
      +  "region"
      +]
  3. Changed4 schema fields changed
    • addedOutput schema / properties / close_news / items / properties / news_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / close_news / items / required
      Previous value: -[
      -  "title",
      -  "source",
      -  "card_url",
      -  "summary",
      -  "age",
      -  "source_url"
      -]New value: +[
      +  "news_id",
      +  "title",
      +  "source",
      +  "card_url",
      +  "summary",
      +  "age",
      +  "source_url"
      +]
    • addedOutput schema / properties / related_news / items / properties / news_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / related_news / items / required
      Previous value: -[
      -  "title",
      -  "source",
      -  "card_url",
      -  "summary",
      -  "age",
      -  "source_url"
      -]New value: +[
      +  "news_id",
      +  "title",
      +  "source",
      +  "card_url",
      +  "summary",
      +  "age",
      +  "source_url"
      +]
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds the login requirement and details the output structure (related_news vs close_news), providing useful behavioral context beyond annotations.

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 two sentences, front-loaded with the primary action and efficiently covering key details. It could be slightly more concise by omitting redundant explanation of the return dict, but it remains compact.

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?

Given the tool's moderate complexity (5 params, 1 required, output schema present), the description adequately covers input requirements, output structure, and access constraints (login). It is complete enough for an agent to use correctly.

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 description coverage is 100%, so the schema already documents all parameters. The description adds marginal value by restating the mutual exclusivity of by_id and by_category and mentioning the output structure, but does not significantly enhance semantic understanding.

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 fetches news related to a topic or specific news item, and explains the two input modes (by_id and by_category). However, it does not explicitly differentiate from siblings like get_news_by_category, which weakens distinction.

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?

It specifies that at least one of by_id or by_category is required, and that login is necessary. It does not, however, provide guidance on when to prefer this tool over siblings or when not to use it.

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