Skip to main content
Glama

Newsdata

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Latest News

latest_news
Read-onlyIdempotent

Get the latest global news headlines and articles — world news, breaking news, and business/financial/stock-market news. Filter by keyword, country (2-letter, e.g. "us"), category (business, technology, politics, sports, health, science), and language. IMPORTANT: for stock-market / financial-market / economy / "world market news" questions, ALWAYS pass category: "business" — it returns real market-news outlets and filters out low-quality SEO/crypto-promo articles. Returns article title, description, link, source, publish date, category, and country. Paginate via the nextPage token. Examples: latest_news({ query: "stock market", category: "business" }) for world market news; latest_news({ query: "election", country: "us", category: "politics" }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNonextPage token returned from a prior call, to fetch the next page of results
queryNoKeywords to search news articles for. Every term is AND-ed — each word must appear in the article — so use 1-3 distinctive keywords ("NMPA approval biotech", "AI chips") rather than a full phrase; "Chinese biotech out-licensing deals NMPA approvals" returns 0 results while "NMPA Chinese biotech" returns articles.
_apiKeyNoOptional — your own NewsData.io API key for higher limits; omit to use the shared Pipeworx key.
countryNo2-letter country code to filter news by, e.g. "us", "gb", "in"
categoryNoNews category, e.g. "business", "technology", "politics", "sports", "health", "science". OMIT unless confident — a wrong category guess returns 0 results (e.g. drug-approval and pharma-industry stories are categorized "business", not "health").
languageNoLanguage code to filter news by, e.g. "en", "es", "fr"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"News category, e.g. \"business\", \"technology\", \"politics\", \"sports\", \"health\", \"science\""New value: +"News category, e.g. \"business\", \"technology\", \"politics\", \"sports\", \"health\", \"science\". OMIT unless confident — a wrong category guess returns 0 results (e.g. drug-approval and pharma-industry stories are categorized \"business\", not \"health\")."
    • changedInput schema / properties / query / description
      Previous value: -"Keyword or phrase to search news articles for, e.g. \"election\", \"AI chips\""New value: +"Keywords to search news articles for. Every term is AND-ed — each word must appear in the article — so use 1-3 distinctive keywords (\"NMPA approval biotech\", \"AI chips\") rather than a full phrase; \"Chinese biotech out-licensing deals NMPA approvals\" returns 0 results while \"NMPA Chinese biotech\" returns articles."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "category": "business",
+    "query": "stock market"
+  },
+  {
+    "category": "politics",
+    "country": "us",
+    "language": "en",
+    "query": "election"
+  }
+]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses return fields (title, description, link, source, publish date, category, country), pagination via nextPage token, and filtering behavior (business category filters out SEO/crypto-promo content). It also warns about zero results for wrong category guesses, adding significant behavioral context.

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 compact but information-dense, with a clear flow: purpose, filters, critical note, return fields, pagination, examples. Every sentence adds distinct value, and the front-loaded first sentence immediately establishes the tool's core function.

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

Completeness5/5

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

No output schema exists, so listing return fields is essential—done. Pagination, parameter usage, and edge-case warnings (zero results) are covered thoroughly. With 6 optional parameters and rich examples, the description fully equips an agent to use the tool correctly in varied scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by illustrating parameter combinations with examples (query+category, query+country+category+language) and by emphasizing the business category behavior, which is critical for effective use. However, it doesn't deeply elaborate on type formats beyond what the schema already explains.

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 opens with a specific verb+resource: 'Get the latest global news headlines and articles' and clearly enumerates coverage areas (world news, breaking news, business/financial/stock-market). It distinguishes itself from sibling tools like crypto_news by stating 'global' and including multiple categories, making the scope unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance with capitalized 'IMPORTANT' instruction for stock-market queries to pass category 'business', plus concrete examples for world market news and election news. It also implies alternatives by noting category behavior and omitting crypto, which differentiates from sibling crypto_news.

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

All Newsdata 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