TipRanks

get_assets_news

Read-onlyIdempotent

Returns recent news articles for tickers, aggregated from many news sites, each with a sentiment tag and source URL (headlines only — no article body). For general/market TipRanks news without a specific ticker, or for an article excerpt, use get_latest_news.

This tool serves the CURRENT news window only: it returns each ticker's most
recent articles, and from_date just trims that recent set. For news from a
specific past date range, use get_latest_news with from_date + to_date,
which searches the full archive.

Args:
    tickers: Comma-separated ticker symbols
    count: Number of articles to return (default 10)
    from_date: Optional 'YYYY-MM-DD' recency floor (filtered on `date`).

Returns JSON: {"assetNewsArticles": [...]}. Each entry:
  - ticker, companyName
  - sentiment: bucketed signal — one of "VeryPositive", "Positive",
      "Neutral", "Negative", "VeryNegative". Derived from TipRanks
      news-sentiment classifier on the article text.
  - siteName, url, title
  - date, addedOn, publishTime, articleTimestamp: redundant date
      fields. addedOn is when TipRanks ingested it; publishTime is
      the source's stated publication time. Prefer publishTime.

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No
`tickers`	Yes
`from_date`	No	Optional recency floor 'YYYY-MM-DD', applied to the recent articles this tool returns. It cannot pull older news into range — for a past date window use get_latest_news with from_date + to_date.

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive nature. The description adds significant context beyond annotations: it explains the tool returns only headlines (no article body), that from_date only trims the recent set rather than pulling older articles, and details the redundant date fields, specifically advising to prefer publishTime over addedOn. This is rich behavioral context with no contradictions.

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?

The description is longer than average but well-structured with 'Args' and 'Returns' sections. The opening sentence immediately conveys the core purpose, and subsequent lines provide necessary detail about behavior, usage limits, and return fields. Some redundancy in listing return fields could be trimmed, but every sentence contributes meaningful information, so it earns a 4 rather than a 5.

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?

The tool has no output schema, so the description fully documents the return structure including the assetNewsArticles container and all fields: ticker, companyName, sentiment bucket, siteName, url, title, and date variants. It also explains the sentiment classifier, the meaning of addedOn vs publishTime, and the tool's limitation to current news. This is complete for a news-retrieval tool with no output schema.

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 description coverage is only 33% (only from_date has schema-level description), so the description must compensate. It does so by explaining 'tickers' as comma-separated symbols, 'count' as number of articles with default 10, and 'from_date' as a recency floor with format and behavioral nuance. Minor mismatch: schema allows tickers as array, but description says comma-separated only, slightly limiting the semantics. Overall adds strong value beyond schema.

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 and resource: 'Returns recent news articles for tickers, aggregated from many news sites, each with a sentiment tag and source URL.' It also explicitly distinguishes itself from get_latest_news, stating this tool is for ticker-specific news and headlines only, which clearly separates it from siblings.

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 and when-not-to-use guidance: 'For general/market TipRanks news without a specific ticker, or for an article excerpt, use get_latest_news.' It also clarifies the tool's limitation to the current news window and instructs to use get_latest_news with from_date + to_date for past date ranges, giving clear alternatives.

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?