TipRanks

get_etf_exposures

Read-onlyIdempotent

Returns the list of ETFs that hold a specific stock, sorted by holding market value (largest first).

Args:
    ticker: Stock ticker (e.g. 'MSFT', 'AAPL')
    page: Page number (default 1)
    page_size: Results per page (default 20, max 100)

Returns per ETF: etfTicker, etfCompanyName, etfCategory, aum, expenseRatio,
holdingWeight (% of ETF in this stock), holdingMarketValue ($),
holdingNumOfShares, weightInAsset (% of stock's outstanding shares held by this ETF),
etfAnalystConsensusScore, etfSmartScore. Also returns totalCount (total ETFs holding the stock).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`ticker`	Yes
`page_size`	No

TDQS

A4.6/5.0

Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds behavioral details beyond these: sorting by holding market value (largest first), pagination behavior (page, page_size defaults and max 100), and the exact list of per-ETF fields returned. This enriches the annotation baseline without contradiction.

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 well-structured with a clear one-sentence purpose, followed by an Args block and a Returns block. Every line adds useful information—parameter defaults, max page_size, and per-ETF fields—with no fluff or repetition.

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 description covers inputs, outputs, sorting, and pagination completely. There is no output schema, so the detailed return fields are essential and provided. Given the tool's moderate complexity and strong annotations, no critical information 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 0%, so the description carries full responsibility. It explains each parameter: ticker with examples, page with default, page_size with default and max. This fully compensates for the lack of schema descriptions and adds practical usage guidance.

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 clearly states 'Returns the list of ETFs that hold a specific stock, sorted by holding market value (largest first).' This uses a specific verb ('Returns'), identifies the resource (ETFs holding a specific stock), and distinguishes it from sibling tools like get_etf_holdings (which likely lists holdings of a given ETF) and get_etf_top_stocks.

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

Usage Guidelines4/5

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

The description implies a clear use case: finding which ETFs hold a given stock, with sorting and pagination details. However, it does not explicitly state when to use this tool over alternatives such as get_etf_holdings or get_etf_screener, nor does it mention exclusions. The context is clear but not explicitly differentiated.

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?