Newsapi

Top Headlines

top_headlines

Read-onlyIdempotent

Fetch current top news headlines from NewsAPI, filterable by country (ISO 2-letter), category (business/entertainment/health/science/sports/technology), publisher sources, or keyword q. Returns article title, description, source, URL, and published date.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "us",
      "category": "technology",
      "pageSize": 10
    },
    "name": "top_headlines"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No
`page`	No
`country`	No
`sources`	No
`category`	No
`pageSize`	No

Output Schema

Name	Required	Description
`status`	No	API response status
`articles`	No	Array of article objects
`totalResults`	No	Total number of results available

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "category": "technology",
+    "country": "us",
+    "pageSize": 10
+  },
+  {
+    "page": 1,
+    "q": "bitcoin",
+    "sources": "bbc-news,cnn"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "articles": {
+      "description": "Array of article objects",
+      "items": {
+        "properties": {
+          "author": {
+            "description": "Article author",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "content": {
+            "description": "Article content",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Article description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "publishedAt": {
+            "description": "Publication timestamp",
+            "type": "string"
+          },
+          "source": {
+            "properties": {
+              "id": {
+                "description": "Source ID",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "name": {
+                "description": "Source name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Article URL",
+            "type": "string"
+          },
+          "urlToImage": {
+            "description": "Image URL for article",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "API response status",
+      "type": "string"
+    },
+    "totalResults": {
+      "description": "Total number of results available",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds return fields and filter options, but it does not disclose important behavioral constraints such as the mutual exclusivity of country/category with sources, or pagination behavior (page/pageSize). These are meaningful traits beyond the annotations.

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?

The description is two sentences, front-loaded with the core purpose, and succinctly lists filters and return fields. Every sentence contributes useful information without redundancy.

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?

With an output schema present, the description's mention of return fields is a bonus. It covers the main filtering options and the tool's purpose, making it largely complete. However, it omits pagination parameters and the restriction on combining sources with country/category, which would be needed for fully reliable invocation.

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 0%, so the description must compensate. It explains 'country' (ISO 2-letter), 'category' (with enumerated values), 'sources', and 'q', but omits 'page' and 'pageSize' entirely. The description adds value for 4 of 6 parameters but is not complete, leaving pagination semantics undocumented.

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 the tool fetches 'current top news headlines' from NewsAPI, with a specific verb ('Fetch') and resource ('top news headlines'). It lists the filtering dimensions (country, category, sources, q), which distinguishes it from generic search tools like 'everything' that search all articles.

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 implies usage for top headlines but does not explicitly state when to use this tool versus the 'everything' sibling (which likely searches all articles). No exclusions or alternative guidance is provided, making the usage context clear but not explicitly differentiated.

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

All Newsapi tools Inspect

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.