Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance custom screen

yahoo_finance_screener_search
Read-onlyIdempotent

Screen Yahoo Finance for stocks, ETFs, crypto, and other instruments using custom filters, sorting, and pagination to identify assets matching specific criteria.

Instructions

Search Yahoo Finance with a custom screener query. Optional inputs: instrumentType, filters, query, sort, order and 3 more. Returns a list (use cursor when paginated).

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yahoo_finance_screener_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort field from the screener field catalogue. Default: `intradaymarketcap` for equity and crypto, `ticker` for other types. An unknown field is refused for equity and ETF screens; other types are sent as given.
limitNoPage size as an integer from 1 to 250. Default: 50.
orderNoSort direction. Default: `desc`, except `asc` (A to Z) when no `sort` is given and the type sorts by `ticker` (ETF, mutual fund, index, future, currency and option).
queryNoRaw screener query as a JSON string, for filters the structured form cannot express. Read-only.
cursorNoPass `page.nextCursor` from the previous response to get the next page.
offsetNoZero-based position to begin the list at. Default: 0; maximum: 1,000,000. Only the first 10,000 rows are available; past that the page is empty.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
filtersNoFilters combined with AND, as a JSON string: an array of {"field", "operator", "value" or "values"} objects. The operator defaults to EQ.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
instrumentTypeNoInstrument type to screen. Default: `equity`. Crypto and currency screens are not limited to US instruments.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a little beyond that—it says the result is a list and that a cursor is used for pagination—but omits behavior the schema warns about, such as the 10,000-row availability ceiling and the conversation_id sequencing rule.

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?

Two short sentences, front-loaded with purpose and followed by scope and return note—nothing is padded. The vague "and 3 more" phrasing is the only real flaw.

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

Completeness2/5

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

This is an 11-parameter tool with pagination edge cases and sequencing rules, and there is no output schema. The description gives only one line about return values and cursor usage, leaving the pagination limits, default sort/order behavior and the two required analytics parameters unexplained.

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 every parameter is already documented in detail (defaults, ranges, enum meanings). The description merely enumerates parameter names and then says "and 3 more," which adds no meaning over the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ("Search") and a specific resource (Yahoo Finance screener), qualified by "custom screener query," which distinguishes it from a plain keyword search. It does not name the sibling that fetches a saved screen (yahoo_finance_screener_get) or the field catalogue tool, so the differentiation is only partial.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. An agent must infer that this tool is for ad-hoc screening with user-supplied filters rather than running a prebuilt screen, and the description never routes to yahoo_finance_screener_fields_list for discovering field names or to yahoo_finance_screener_get for canned screens.

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

Deploy Server

Other Tools