Skip to main content
Glama

Newsapi

by io.github.pipeworx-io

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
pageNo
countryNo
sourcesNo
categoryNo
pageSizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoAPI response status
articlesNoArray of article objects
totalResultsNoTotal number of results available

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • 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"
+}
  2. First observed

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

There are several clusters of tools with overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to data sources; entity_profile, compare_entities, and recent_changes all provide company research. The descriptions are detailed, but an agent could easily misselect among these near-duplicates, especially since ask_pipeworx_beta is explicitly identical to ask_pipeworx right now.

Naming Consistency2/5

Placeholder for naming consistency placeholder

Tool Count1/5

34 tools for a server named Newsapi is an extreme scope mismatch. Only three tools (everything, top_headlines, sources) are news-related; the rest cover data research, prediction markets, memory, subscriptions, and package scanning, which belongs in separate servers. The count is also past the 25+ range that feels overloaded for any single purpose.

Completeness3/5

The three NewsAPI tools themselves cover the standard news surface (top_headlines, everything, sources) with no major gaps. However, the server's stated purpose is diluted by ~30 unrelated tools, and the non-news tools form an incoherent assortment with no clear unified domain to assess completeness against. The mismatch makes completeness hard to reason about and degrades the overall usefulness.

Resources