Skip to main content
Glama
Yahoo Finance MCP Server

Yahoo Finance MCP Server

get_market_news

Read-onlyIdempotent

Retrieve recent news articles and headlines for a stock ticker to identify catalysts or market sentiment. Specify article count and output as Markdown or JSON.

Instructions

Latest news articles for one stock; each item has a title, publisher/source, publish date, a short summary, and a link.

Use for "what's the latest news on X", recent headlines, or catalysts. Returns news only: for price use get_stock_quote, for fundamentals use the financials tools.

count sets how many articles to return (1-20, default 10). Returns Markdown by default, or JSON when response_format='json'. No recent news returns a short message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_market_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of news articles to return (1-20)
tickerYesStock ticker symbol to get news for (e.g., 'AAPL', 'TSLA', 'NVDA')
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown

Output Schema

NameRequiredDescriptionDefault
newsNo
countNo
tickerNo
messageNoSet instead of data when there is nothing to return for this request (for example, no dividends on record).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds behavior annotations don't: the default Markdown vs JSON output switch and, notably, the empty-result case ('No recent news returns a short message'), which prevents an agent from misreading an empty answer as a failure. It stops short of noting source recency or rate limits, so not a 5.

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 paragraphs, front-loaded with purpose, then routing guidance, then output/parameter notes. Every sentence carries distinct information with no repetition of the tool name or filler.

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?

An output schema exists, so return-value structure needn't be spelled out, yet the description still sketches item fields. Combined with the format switch and empty-result behavior, an agent has everything needed to call this correctly for a simple three-parameter read tool.

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 all three parameters are already documented in the schema. The description restates the count range and default and the response_format switch without adding new semantics (e.g., no guidance on picking a count or when JSON is preferred). Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Latest news articles for one stock') and enumerates the fields each item carries (title, publisher/source, publish date, summary, link). An agent can immediately distinguish it from quote, fundamentals, or historical-price siblings.

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

Usage Guidelines5/5

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

Gives an explicit use-case phrase ('what's the latest news on X', recent headlines, catalysts) and names the alternatives with their domains: get_stock_quote for price, the financials tools for fundamentals. The exclusion ('Returns news only') removes any ambiguity about scope.

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