Returns all holdings for one of your TipRanks portfolios.
Per holding: ticker, shares, price, cost basis (AvgExecutionPrice),
P/E ratio, dividend yield, market cap, sector, country, 52-week high/low,
percentage of portfolio, beta, EPS. Plus total value, cash, stock count.
Args:
portfolio_id: One of the IDs returned by list_my_portfolios.
| Name | Required | Description | Default |
|---|---|---|---|
| portfolio_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by detailing the output structure, including per-holding metrics and portfolio summaries (total value, cash, stock count), which is especially important given the absence of an output schema. It does not mention pagination or potential large response sizes, but for a simple read operation this is sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is efficiently organized: a one-line purpose, a field list, and a parameter explanation. Every sentence contributes meaningful information, and the field list is concise yet comprehensive. It is not bloated and earns its length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read tool with high annotation coverage, the description is almost complete. It covers the return values thoroughly and the parameter provenance. The only gaps are potential edge cases (e.g., empty portfolio, invalid ID) or response size limits, but these are not critical for a holdings retrieval tool. Thus it scores just above the minimum viable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides only the type and requirement for portfolio_id with zero coverage. The description compensates fully by explaining that portfolio_id is 'One of the IDs returned by list_my_portfolios,' giving the agent a precise source for the parameter. This transforms an opaque integer into a well-defined reference.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool 'Returns all holdings for one of your TipRanks portfolios,' which is a specific verb+resource. It distinguishes itself from sibling tools like get_portfolio_overview and get_portfolio_analysis by focusing on holdings, and it enumerates the exact data fields returned (ticker, shares, price, cost basis, etc.), leaving no ambiguity about its purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description specifies the prerequisite that portfolio_id comes from list_my_portfolios, which guides the user on how to obtain a valid input. It does not explicitly contrast with sibling portfolio tools, but the context is clear enough that this is the go-to for detailed holdings while other tools handle overviews or analysis. A brief note about when not to use it would elevate this score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.