Skip to main content
Glama

Newsapi

by io.github.pipeworx-io

Everything

everything
Read-onlyIdempotent

Search the NewsAPI article archive by keyword q, source domains, date range (from/to), or language. Sortable by relevancy, popularity, or publishedAt. Returns article title, description, source, content snippet, URL, and published date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
toNo
fromNo
pageNo
sortByNo
domainsNo
sourcesNo
languageNo
pageSizeNo
qInTitleNo
excludeDomainsNo

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: +[
+  {
+    "pageSize": 20,
+    "q": "artificial intelligence",
+    "sortBy": "publishedAt"
+  },
+  {
+    "from": "2024-01-01",
+    "language": "en",
+    "pageSize": 50,
+    "qInTitle": "election",
+    "to": "2024-12-31"
+  }
+]
    • 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.5/5.0
Behavior3/5

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

Annotations already indicate a safe, read-only, idempotent operation (readOnlyHint=true, destructiveHint=false). The description adds useful context about return fields and sort options, but does not disclose any behavioral edge cases (e.g., rate limits, pagination defaults, content truncation). With annotations covering the safety profile, this is acceptable but not rich.

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?

Two sentences, front-loaded with the primary purpose. The first sentence covers core functionality and the second lists return fields. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 11 parameters and no required fields, the description covers the primary search dimensions but misses pagination, source/exclusion filtering, and qInTitle. It is adequate for a basic search but leaves several functional gaps uncovered.

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?

The schema has 0% description coverage, so the description must compensate. It explains key parameters (q, domains, from/to, language, sortBy) and even clarifies sortBy values, but omits page, pageSize, sources, excludeDomains, and qInTitle. This is partial compensation for a large parameter set.

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 searches the NewsAPI article archive via specific criteria (keyword, domains, date range, language), which is a specific verb+resource. It distinguishes the archive scope from siblings like top_headlines, but does not explicitly name any alternative tool, so it falls short of a 5.

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 article archive searches by describing the query parameters, but it provides no explicit guidance on when to prefer this over siblings (e.g., top_headlines for breaking news, search_within for narrower searches). There are no usage exclusions or alternative tool references.

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