Should I use expertUID or the analyst name?

Use expertUID when available because it is the stable identity. Exact analystName lookup is supported, with firmName available only to disambiguate same-name matches.

Does Pineify calculate its own analyst ranking?

No. Success rate, excess return, rank, stars, and summary values are provider-reported fields. Pineify normalizes the result and exposes missing evidence without inventing a score.

Why can performance be unavailable while coverage exists?

The sections use different evidence and time semantics. An analyst can have active calls at the as-of date while the selected lookback has no valid provider performance sample.

Can AI predict stock prices with this MCP tool?

No. AI cannot predict stock prices with certainty, and this MCP tool does not promise future returns. It gives an agent bounded data or validation results that still require independent review, risk controls, and source checking.

Agent workflows

Analyst Track Record MCP Tool for AI Agents

analyze-analyst-track-record resolves one TipRanks analyst by expertUID or exact full name, then returns the provider profile, provider-reported lookback metrics, and bounded point-in-time active stock coverage. Ambiguous names fail explicitly, zero-sample metrics remain unavailable, and Pineify does not create a proprietary analyst score.

Connect Pineify MCP View all MCP tools

MCP tool name

analyze-analyst-track-record

Example prompt

Use Pineify analyze-analyst-track-record with expertUID "EXPERT_UID_FROM_CONSENSUS" over 1y at compact detail. Separate provider performance from active stock coverage and do not score the analyst yourself.

Direct answer

What analyze-analyst-track-record does

Use expertUID when available. Name lookup requires a case-insensitive exact full-name match; firmName can disambiguate that name, and unresolved ambiguity returns an error with at most ten safe candidates.

Performance metrics and active stock coverage have different time semantics: performance uses the selected 1y or 3y lookback, while coverage describes point-in-time active calls as of the requested date.

Contract

What the agent sends and receives

Inputs

Provide exactly one identity: `expertUID`, or `analystName` as an exact full name. Each value is bounded text, not a fuzzy-search prompt.
`firmName`: optional and valid only with `analystName`; it is used to disambiguate exact same-name matches.
`asOfDate`: optional real calendar date no later than the current New York date; omitted means the current New York date.
`lookback: "1y" | "3y"`: optional; `1y` is the default. `detail: "compact" | "standard"` defaults to standard and caps active coverage at 10 or 25 items.

Structured output

`analyst-track-record-v1` structured content with `analyst-track-record-methodology-v1`, resolved expertUID, effective date range, retrieval time, and informational-only marker.
Resolved analyst profile, nullable provider-reported performance summary, and covered or no-coverage active stock calls.
Per-section coverage, earliest/latest opinion dates, collection totals, invalid/truncated counts, sources, warnings, and partial status preserve data boundaries.

Capabilities

Where this MCP tool fits

Resolve one analyst safely

Accepts exactly one of expertUID or analystName, with optional firmName only for name disambiguation, and rejects inconsistent identities.

Return provider-reported performance

Preserves nullable success rate, excess return, rank, stars, URLs, and summary fields without creating a Pineify analyst score.

Inspect current stock coverage

Returns the analyst’s point-in-time active calls with collection bounds, opinion dates, no-coverage state, sources, warnings, and partial status.

Agent workflow

A bounded call from question to review

1
Resolve the analyst identity
Prefer a public expertUID from a prior consensus result; otherwise use the exact analyst full name and optionally the firm.
2
Separate performance from coverage
Interpret provider summary metrics over the selected lookback independently from point-in-time active stock calls.
3
Honor unavailable evidence
Keep zero-sample summaries, nullable profile metrics, partial sources, and no-coverage states explicit rather than estimating replacements.

Prompt examples

Questions an agent can route to this tool

"Use Pineify analyze-analyst-track-record with expertUID "EXPERT_UID_FROM_CONSENSUS" over 1y at compact detail. Separate provider performance from active stock coverage and do not score the analyst yourself."

"Analyze the 3y track record for analystName "EXACT FULL NAME" and firmName "EXACT FIRM NAME" at standard detail. Stop with the ambiguity error if identity is not unique."

"Use this public expertUID to inspect the analyst as of 2026-06-30. Report nullable provider metrics, the active coverage date range, and every warning without predicting future performance."

Operator notes

How I review the result

I use exact identity semantics so two analysts with similar or identical names are not silently merged.

I attribute success rate, excess return, rank, and stars to the provider and keep them nullable when the provider has no valid sample.

Boundaries to keep in the prompt

Name lookup is exact rather than fuzzy. Missing matches and ambiguous same-name results are explicit errors; the tool does not guess an identity.
Provider metrics may be null or unavailable, and historical coverage is limited to the supported recent three-year retention window.
Active stock coverage is a point-in-time view and is not the same as the number of opinions in the selected performance window.
The tool does not predict future analyst accuracy, recommend securities, execute trades, or provide personalized investment advice.

Pineify MCP is an information and code-validation tool, not investment advice. It does not promise returns, place trades, or modify a portfolio. Review timestamps, source fields, code diagnostics, and risk assumptions before acting.

MCP tool family