Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Stack Overflow question answers

stack_overflow_question_answers_list
Read-onlyIdempotent

Lists answers to a Stack Overflow question by votes, activity, or creation time, including answer text and optional comments.

Instructions

List the answers to a Stack Overflow question by votes, activity or time, with their text and, if asked, their comments. Requires questionId. 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": {
      "questionId": "<questionId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "stack_overflow_question_answers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoStack Exchange site, by its API name (`askubuntu`, `serverfault`, `math`, `ru.stackoverflow`). Default: `stackoverflow`. The sites endpoint lists them all.
sortNoOrder of the answers: `votes` (default), `activity` or `creation`. Only `creation` pages without a ceiling.
limitNoUp to this many rows per page, 1 to 100. Default: 30. A page can hold fewer than `limit` rows where rows share a creation second or a block of 100 rows ends. Follow `page.nextCursor` until `hasMore` is false.
orderNoDirection of the sort: `desc` (default) or `asc`.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNo`comments` adds each answer's comments. Default: none.
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.
questionIdYesRequired. Question id on the chosen site, e.g. `11227809`.
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 covered. The description adds that results are a list requiring cursor-based paging and that comments are only fetched when requested, but it does not go further than the schema already does on ordering ceilings or rate behavior.

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?

Three short sentences, front-loaded with the core action and filtering dimension, with the requirement and pagination note following. The final sentence ('Returns a list (use cursor when paginated)') largely repeats what the pagination parameters already encode.

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 10-parameter read-only listing tool with no output schema, the description covers the action, the required identifier, optional comment expansion and paging. The unusual analytics parameters (context, llm_model, conversation_id) are fully documented in the schema, so nothing critical is missing from the description.

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 the baseline is 3. The description restates `questionId` as required and gestures at `sort` and `include: comments`, but it calls the third sort mode 'time' while the enum value is `creation`, a small mismatch that could mislead rather than clarify.

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 (list the answers to a Stack Overflow question) plus the ordering dimension and payload (text, optional comments). It is clearly distinct from siblings such as stack_overflow_user_answers_list or stack_overflow_post_comments_list, though it never names an alternative explicitly.

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?

It states the hard requirement (`questionId`) and gives pagination advice ('use cursor when paginated'), which is practical invocation guidance. However, it says nothing about when to prefer this over the sibling answer-listing or comments tools, and gives no exclusions or prerequisites beyond the required id.

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