TipRanks

get_latest_news

Read-onlyIdempotent

Latest TipRanks news articles (newest first) from TipRanks's own editorial/wire feed — each with a text excerpt, unlike get_assets_news.

Use for general market news (no ticker), news on a specific stock with a
short summary of each story, or to browse a news category. This is also the
tool for news from a specific PAST date range — pass from_date AND to_date
together; the archive holds years of stories, so a past window is answerable
here even though get_assets_news only reaches recent articles.

Args:
    tickers: Optional comma-separated tickers to filter by (e.g. 'NVDA,AAPL').
             Omit for general market news.
    category: Optional single category (see the field description).
    from_date: Optional 'YYYY-MM-DD' recency floor.
    limit: Max articles to return (default 20).
    to_date: Optional 'YYYY-MM-DD' inclusive upper bound. Results are
             newest-first, so from_date alone returns today's news rather
             than news from around that date — add to_date to scope a window.

Returns a JSON list of {id, title, excerpt, author, category, date, url,
tickers}. To read a full article, pass its url or id to get_article.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`tickers`	No
`to_date`	No	Optional 'YYYY-MM-DD' upper bound on the publish date, inclusive of that whole day. Pair with from_date to read a specific past window; from_date on its own returns the newest stories since that date.
`category`	No	Optional single category: 'news', 'the-fly', 'blurbs', 'catalyst', 'ratings', 'cryptocurrencies', 'insider-trading', 'newswire', 'private-companies', 'company-announcements'. Omitted = editorial/wire feed (excludes auto-ingested company-announcements).
`from_date`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / tickers / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / tickers / type
```
Removed value: -"string"
```

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_latest_newsOutput",
-  "type": "object"
-}New value: +null

Changed1 schema field changedAug 12, 2026

addedInput schema / properties / to_date

Added value: +{
+  "default": "",
+  "description": "Optional 'YYYY-MM-DD' upper bound on the publish date, inclusive of that whole day. Pair with from_date to read a specific past window; from_date on its own returns the newest stories since that date.",
+  "title": "To Date",
+  "type": "string"
+}

First observedJul 21, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld/destructive, so the safety profile is free. The description adds genuinely useful behavior beyond that: newest-first ordering, an archive holding years of stories, the excerpt field, and the handoff to get_article. It does not mention pagination limits, rate limits, or what happens when tickers/category are combined, which keeps it short of a 5.

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?

Front-loaded with the core purpose and the sibling contrast in the first sentence, then structured Args and a Returns line. Slightly verbose — the same-point repetition about from_date/to_date appears in both the prose and Args — but every section earns its place for a 5-parameter tool.

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?

With no output schema present, the description carries the return contract itself ({id, title, excerpt, author, category, date, url, tickers}) and the follow-up path via get_article. Combined with full parameter semantics and annotation-covered safety, nothing an agent needs to invoke this correctly is missing.

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

Parameters5/5

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

Schema description coverage is only 40%, and the description fully compensates with an Args block covering all five parameters, including the non-obvious semantics that from_date is a recency floor and that from_date alone returns today's news rather than stories from around that date. This is meaning the schema alone does not supply.

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?

States a specific verb+resource and scope: 'Latest TipRanks news articles (newest first) from TipRanks's own editorial/wire feed'. It explicitly distinguishes itself from get_assets_news (text excerpt, archive depth) and routes to get_article for full reads, so an agent can tell it apart from siblings without opening any schema.

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?

Explicitly enumerates the use cases — general market news with no ticker, ticker-filtered news with summaries, category browsing, and past date-range retrieval — and names the alternative (get_assets_news) plus the condition that selects this tool over it ('get_assets_news only reaches recent articles').

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

All TipRanks 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.

Resources

Need Help?