Yahoo Finance MCP Server

Insider activity

get_insider_activity

Read-only

Fetch insider trading activity for a Yahoo Finance symbol to see individual transactions, a 6-month buy/sell summary, and the current insider roster. Works for equities only.

Instructions

Get insider trading activity for a Yahoo symbol.

Returns individual insider transactions, a 6-month purchases/sales summary, and the current insider roster. 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 insider transactions/roster rows 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_insider_activityArguments"
```
- removedOutput schema / title
```
Removed value: -"get_insider_activityDictOutput"
```
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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context on top: the three-part return shape and, importantly, the equity-only constraint with a defined failure mode for ETF/fund/crypto symbols. It does not discuss pagination or how the 6-month window is computed, which keeps it short of 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 sentences, front-loaded with the action, then returns, then the constraint. No filler, no restatement of the title.

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 covering the safety profile, and an output schema covering the response, the description supplies everything else an agent needs: what comes back and the one input class that fails.

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% and both parameters (symbol formats, limit bounds) are fully documented in the schema, so the baseline of 3 applies. The description adds no format or default information beyond what the schema already states.

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?

"Get insider trading activity for a Yahoo symbol" pairs a specific verb with a specific dataset, then itemizes the three payloads (individual transactions, 6-month purchases/sales summary, insider roster). That distinguishes it from the nearest sibling, get_holders, without the agent needing to open either schema.

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 is only implied: call it with a symbol when insider data is wanted. There is no explicit when-to-use or when-not-to-use versus siblings such as get_holders or get_company_info, and the 'use search first for a company name' routing lives in the schema, not the description.

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