Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance screener page

yahoo_finance_screener_get
Read-onlyIdempotent

Fetch one paginated page from a Yahoo Finance predefined screener, such as most actives or equity lists, with sorting, page size, and cursor controls for pulling the next results.

Instructions

Get one page of a Yahoo Finance predefined screener. Requires screenerId. 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": {
      "screenerId": "<screenerId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yahoo_finance_screener_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort field from the screener field catalogue. Default: the screener's own order. 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`.
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.
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.
screenerIdYesRequired. Predefined screener id from the screeners list, e.g. `equity` or `MOST_ACTIVES`.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the pagination behavior and the required-parameter constraint, but omits the 10,000-row availability cap and the sort-field refusal behavior that live only in the schema.

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 core action, then the requirement, then the return shape. No wasted wording.

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?

For a 9-parameter read tool with full schema coverage and no output schema, the description covers the action, the required input, and the return shape adequately. It could say more about the row cap and sort validation, but the schema carries those details.

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 including sort, limit, offset, and cursor is already documented in the schema. The description only restates the screenerId requirement and the cursor pagination hint, adding little beyond the structured data. 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?

States a specific verb and resource ('Get one page of a Yahoo Finance predefined screener') and notes the required screenerId, so the agent knows exactly what it retrieves. It does not distinguish itself from the sibling yahoo_finance_screener_search, leaving the boundary between the two to inference.

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?

Gives a concrete usage cue for pagination ('use cursor when paginated') and flags the required parameter, but offers no guidance on when to pick this over yahoo_finance_screener_search or yahoo_finance_screeners_list. Usage is implied rather than stated.

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