Yahoo Finance MCP Server

News

get_news

Read-only

Retrieve recent news headlines for a Yahoo Finance symbol (ticker or ISIN), with an optional 1-50 article limit and details such as title, summary, publisher, publish time, and URL.

Instructions

Get recent news headlines for a Yahoo symbol (up to limit, 1-50).

Each article includes title, summary, publisher, publish time, and URL. source is ticker for Yahoo's news on the symbol. When that has none, source is search for the articles Yahoo's search tags with it, which have no summary and are rarely found for symbols outside the US.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of headlines 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.

Changed1 schema field changedv0.12.0Nov 4, 2026
- changedInput schema / properties / limit / maximum
```
Previous value: -10New value: +50
```
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_newsArguments"
```
- removedOutput schema / title
```
Removed value: -"get_newsDictOutput"
```
Changed1 schema field changedv0.7.0Oct 1, 2026
- addedInput schema / properties / symbol / maxLength
```
Added value: +32
```
Changed1 schema field changedv0.6.0Sep 26, 2026
- changedInput schema / properties / limit / maximum
```
Previous value: -30New value: +10
```

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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real value on top by explaining the two-tier source fallback, the fields each article carries, and the limitation that search-sourced results omit summaries and are rare outside the US. The only gap is that it does not describe ordering or freshness of 'recent' headlines, though an output schema exists that likely covers return shape.

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?

Four short sentences, front-loaded with the core action and then the return contents, with only the parenthetical limit range as slight redundancy against the schema. The final sentence about `search` sourcing is a bit dense but earns its place by explaining a real caveat.

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?

For a two-parameter read tool with full schema coverage, annotations, and an output schema, the description covers action, return contents, source semantics, and known data-quality caveats. There is little an agent would need to know before calling it that is missing.

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 coverage is 100%, so both parameters are already documented, and the description's restatement of the 1-50 limit range duplicates the schema's minimum/maximum. The genuinely additive part is the implied relationship between symbol resolution and the source field, but that is indirect rather than an explanation of the parameters themselves.

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 definition opens with a specific verb and resource ('Get recent news headlines for a Yahoo symbol') and constrains scope with the limit range. It is unambiguous against siblings like get_quote or get_company_info, which return price or profile data rather than headlines.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: the fallback from `ticker` to `search` sources tells the agent what to expect, and the note that search-sourced articles lack summaries helps set expectations. However, there is no explicit guidance on when to call this tool versus alternatives such as search or get_company_info, and the 'use search first for a company name' hint lives only in the schema.

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