Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance call transcript

yahoo_finance_transcript_get
Read-onlyIdempotent

Fetch a Yahoo Finance earnings-call transcript, including speakers and paragraphs, by ticker symbol and transcript event ID.

Instructions

Get Yahoo Finance earnings-call transcript with speakers and paragraphs. Requires symbol and eventId.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesRequired. Ticker symbol, case-insensitive, e.g. `AAPL`, `^GSPC`, `EURUSD=X`, `BTC-USD`, `7203.T`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
eventIdYesRequired. Transcript event id from the transcripts list, 1 to 9999999999.
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.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered and the bar is lower. The description adds that the payload includes speakers and paragraphs, which is useful, but it omits the required conversational protocol (context, llm_model, conversation_id echo) and says nothing about transcript length or truncation. Adequate rather than rich.

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 and waste-free, with the returned content stated before the prerequisites. Minor deduction for the second sentence, which partially repeats the schema's required list and states it incompletely (four parameters are required, not two).

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?

This is a simple read-only single-resource fetch whose annotations carry the safety profile, whose schema fully documents parameters, and which has no output schema, so the description only needs to convey purpose, prerequisites, and return shape. It does all three, though it leaves the eventId provenance and the transcript size to inference.

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 five parameters are already documented in detail, including the symbol pattern, the eventId range, and the conversation_id echo rule; the baseline of 3 applies. The description only echoes symbol and eventId and ignores the three other required parameters, adding nothing the schema does not already provide.

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 names a specific verb and resource (get ... earnings-call transcript) and distinguishes itself from the sibling yahoo_finance_transcripts_list by being the single-transcript fetch. It also adds a content hint (speakers and paragraphs) that tells the agent what it returns. It does not explicitly state the list-vs-get relationship, so it is strong but not fully differentiated.

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?

'Requires `symbol` and `eventId`' implies the prerequisite that an event id must be obtained first, but the description never points to yahoo_finance_transcripts_list as the source of eventId (that hint lives only in the schema). There are no when-not-to-use statements or named alternatives, so guidance is only implied.

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