Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Stack Overflow user answers

stack_overflow_user_answers_list
Read-onlyIdempotent

List answers a Stack Overflow user has posted, ordered by activity, votes, or creation time, to review their contributions. Provide a member ID and paginate results as needed.

Instructions

List the answers a Stack Overflow user has given, by activity, votes or time. Requires memberId. 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": {
      "memberId": "<memberId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "stack_overflow_user_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: `activity` (default), `creation` or `votes`. Only `creation` pages without a ceiling; `activity` and `votes` stop at the list ceiling. Rows with equal scores can repeat or skip.
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`body` adds the answer text (HTML and Markdown) to each row. Default: none.
memberIdYesRequired. User id on the chosen site, e.g. `22656`. `-1` is the Community user.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds that the result is a list and that pagination is cursor-based, but says nothing about the list ceiling, ordering stability, or rate limits that the schema hints at.

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 with the resource and sort options front-loaded; the parenthetical cursor hint is the only mildly redundant element. Nothing is wasted, but the final sentence is thinner than it could be.

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

Completeness3/5

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

For a 10-parameter tool with no output schema, the description covers purpose and pagination but omits the return shape beyond "a list" and never mentions the site, include=body, or the conversation_id/llm_model conventions. The rich schema compensates, leaving this adequate but not complete.

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 coverage is 100%, so every parameter including site, limit, order, include and cursor is already documented in the schema. The description restates the required memberId and the sort choices without adding syntax or format detail, so the 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 ("List the answers a Stack Overflow user has given") with the sort axes, which implicitly separates it from stack_overflow_question_answers_list. It does not explicitly name that sibling or state the contrast, so it falls short of a 5.

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?

The scoping to a specific user implies when the tool applies versus question- or post-scoped siblings, but there is no explicit when/when-not statement or named alternative. The cursor note is an operational instruction for pagination, not selection guidance.

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