Yahoo Finance MCP Server

Rating changes

get_upgrades_downgrades

Read-only

Retrieve recent analyst rating changes (upgrades/downgrades) for a Yahoo Finance stock symbol, showing firm, from/to grade, and action, most recent first.

Instructions

Get recent analyst rating changes (upgrades/downgrades) for a Yahoo symbol.

Each entry is a firm's rating change with the from/to grade and action, most recent first. Equity-only: an ETF, fund or crypto symbol answers with an error that says so.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of rating changes to return.
`symbol`	Yes	A Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.8.6Oct 17, 2026
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / symbol / title
```
Removed value: -"Symbol"
```
- removedInput schema / title
```
Removed value: -"get_upgrades_downgradesArguments"
```
- removedOutput schema / title
```
Removed value: -"get_upgrades_downgradesDictOutput"
```
Changed1 schema field changedv0.7.0Oct 1, 2026
- addedInput schema / properties / symbol / maxLength
```
Added value: +32
```

Changed1 schema field changedv0.4.0Aug 18, 2026

changedInput schema / properties / symbol / description

Previous value: -"A native Yahoo Finance ticker symbol, e.g. 'AAPL', 'MSFT', 'SAP.DE', or 'BMW.DE'. This is NOT an ISIN, a WKN, or a company name, and must NOT be built by appending an exchange suffix to an ISIN (e.g. 'US0378331005.DE' is invalid). If you only have a name or ISIN, call the 'search' tool first and pass the 'symbol' value it returns."New value: +"A Yahoo ticker or an ISIN, e.g. 'AAPL', 'SAP.DE' or 'US0378331005'. For a company name, use 'search' first."

First observedv0.2.2Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds useful behavior: entries are the from/to grade and action, ordered most-recent-first, and non-equity symbols fail with an explicit error. It does not mention rate limits or the size/shape of the underlying response beyond the entry description.

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?

Three short, front-loaded sentences: purpose, return content, and the equity-only constraint. No filler, and the most decision-relevant information comes first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, annotations covering safety, and full parameter docs, the description only needs to add what structured fields cannot; it does that via the equity-only error behavior and ordering. The lone gap is that 'recent' is never quantified, leaving the agent unsure of the time window.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both 'symbol' and 'limit' are already fully documented (including the ISIN/ticker examples and the 'use search first' tip). The description adds no parameter-level syntax or constraints beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get recent analyst rating changes (upgrades/downgrades)') scoped to a Yahoo symbol, which an agent can distinguish from sibling tools like get_recommendations or get_estimates. It also declares the shape of each entry (firm, from/to grade, action), so the agent knows what it will get.

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?

Gives a real when-not condition: 'Equity-only: an ETF, fund or crypto symbol answers with an error that says so,' which steers the agent away from misuse. It does not name an alternative when the symbol is not an equity or when analyst-recommendation summaries are wanted, so routing to siblings is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.