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

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description reveals important behavioral traits: the newest-first ordering, the presence of excerpts (which get_assets_news lacks), the archive depth ('holds years of stories'), the counterintuitive from_date behavior ('from_date alone returns today's news rather than news from around that date'), and the inclusive to_date. It also states the return format and forwards to get_article for full content. This is rich context not captured by 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 longer than the minimal examples, but every sentence earns its place. It is structured with a purpose statement, usage guidance, an Args list, and return format. It front-loads the core purpose and differentiator, then provides necessary details without repetition or filler. The length is justified by the need to explain 5 parameters and subtle date-window semantics.

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, the description appropriately specifies the returned structure: 'a JSON list of {id, title, excerpt, author, category, date, url, tickers}.' It also covers enough context for the tool's use cases, edge cases (date windows), and relationships to sibling tools (get_assets_news, get_article). Given the moderate complexity (5 optional parameters) and the absence of an output schema, this description is complete and self-sufficient.

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 coverage is only 40% (category and to_date have descriptions), but the description compensates with a full Args list explaining each parameter: tickers as comma-separated, category as single optional value, from_date as a 'YYYY-MM-DD' recency floor, limit with default 20, and to_date as an inclusive upper bound. It also clarifies the interaction between from_date and to_date, which the schema does not fully convey. This directly addresses the low schema coverage.

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 statement: 'Latest TipRanks news articles (newest first) from TipRanks's own editorial/wire feed — each with a text excerpt, unlike get_assets_news.' This clearly defines what the tool does and immediately differentiates it from a sibling tool. It also lists concrete use cases: general market news, stock-specific news with summaries, and browsing categories.

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?

Explicit guidance is provided: 'Use for general market news (no ticker), news on a specific stock... or to browse a news category.' It also states when this tool is uniquely appropriate: 'This is also the tool for news from a specific PAST date range — pass from_date AND to_date together...' and contrasts with get_assets_news's limited recency. This gives clear when-to-use and even notes when not to rely on the alternative.

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

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.8/5.0

Disambiguation3/5

Many tools have overlapping purposes, e.g. get_etf_analysis vs get_etf_forecast both provide ETF analyst consensus, get_etf_holdings vs get_etf_top_stocks both list constituents, and get_portfolio_overview vs get_portfolio_performance both return returns/performance. The detailed descriptions help, but the sheer number of similar tools creates ambiguity in selection.

Naming Consistency4/5

The set is largely consistent with a 'get_' prefix and descriptive nouns (get_stock_quotes, get_crypto_quote, get_dividend_history). Minor deviations include 'list_my_portfolios' instead of 'get_my_portfolios' and singular/plural variants like get_all_commodities_quotes vs get_commodity_quote, but the pattern remains predictable.

Tool Count1/5

With 71 tools, the count far exceeds the 50+ threshold described as an extreme mismatch. Even though the server covers a broad financial domain, such a large surface is overwhelming for an agent and includes many redundant or highly specific tools that could be consolidated.

Completeness5/5

The tool set provides comprehensive coverage of TipRanks data: quotes and historical data for all major asset classes, news, earnings and economic calendars, analyst and sentiment data, financial statements, technical analysis, options, portfolios, and screeners. There are no obvious dead ends for typical financial research tasks.

Resources

Need Help?