Skip to main content
Glama

NewzAI News MCP server

by ai.newzai.api
OverviewDiscussionsAdmin

get_news_by_category

Read-only

Fetches news for a predefined category with full details including title, source, summary, age, card_url, and source_url. Specify the predefined category for which you want the news, the required region of source of news and the OUTPUT language of news. If the user has not provided a country or region, ask them which region they want before calling this tool. Note: Language is not a filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_kNoNumber of news items to fetch
regionYesRequired region for the news. If missing from the user's request, ask the user which region/country they want.
languageNoLanguage of the output of the news content. It is not a filter, news in other languages may also be included if output language is differenten
predefined_categoryYesPredefined category to search (e.g., TECHNOLOGY, BUSINESS)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / region / enum
      Previous value: -[
-  "india",
-  "united-states",
-  "united-kingdom",
-  "japan"
-]New 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 from where one want to get news of the predefined category"New value: +"Required region for the news. If missing from the user's request, ask the user which region/country they want."
    • changedInput schema / required
      Previous value: -[
-  "predefined_category"
-]New value: +[
+  "predefined_category",
+  "region"
+]
  3. Changed1 schema field changed
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
-  {
-    "items": {
-      "properties": {
-        "age": {
-          "type": "string"
-        },
-        "card_url": {
-          "type": "string"
-        },
-        "source": {
-          "type": "string"
-        },
-        "source_url": {
-          "type": "string"
-        },
-        "summary": {
-          "type": "string"
-        },
-        "title": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "title",
-        "source",
-        "card_url",
-        "summary",
-        "age",
-        "source_url"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "properties": {
+        "age": {
+          "type": "string"
+        },
+        "card_url": {
+          "type": "string"
+        },
+        "news_id": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        },
+        "source_url": {
+          "type": "string"
+        },
+        "summary": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "news_id",
+        "title",
+        "source",
+        "card_url",
+        "summary",
+        "age",
+        "source_url"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  4. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by explaining the output fields (title, source, summary, etc.) and clarifying that language is not a filter. No contradictions; the description enhances transparency 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 core purpose, and includes essential details without fluff. It is appropriately sized but could be more structured (e.g., bullet points).

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 that an output schema exists, the description does not need to explain return values. It covers the key behaviors: category, region requirement, and language note. A minor gap is the lack of guidance for choosing between this and sibling tools, but overall it is complete for a simple fetch tool.

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 baseline is 3. The description adds the instruction to ask for region if missing and reiterates the purpose of each parameter, but adds little new meaning beyond the schema. The additional context is minor.

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 it fetches news for a predefined category with full details. The verb 'fetches' and noun 'news' are specific, and it lists the included fields. However, it does not differentiate from sibling tools like search_news or get_news_headlines, which reduces clarity slightly.

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?

The description instructs to ask for region if missing and notes that language is not a filter, which are helpful guidelines. However, it does not specify when to use this tool versus alternatives (e.g., get_news_by_preference or search_news), leaving some ambiguity.

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

All NewzAI News MCP server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources