Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Stack Overflow user comments

stack_overflow_user_comments_list
Read-onlyIdempotent

Lists the comments a Stack Overflow user has written, ordered by creation time or votes. Requires a member ID and returns paginated results via cursor.

Instructions

List the comments a Stack Overflow user has written, by time or votes. 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_comments_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: `creation` (default) or `votes`. `creation` pages without a ceiling; `votes` stops 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.
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

A3.5/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 structurally and the bar for the description is lower. The description adds only the return shape ('Returns a list') and a cursor hint, both of which the schema's cursor and limit descriptions already cover in more detail.

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 with the core action front-loaded, and nothing is buried. Minor waste in 'Returns a list,' which is self-evident for a list tool, and in repeating the required-parameter fact already in the schema.

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?

The tool has 9 parameters but the schema documents every one thoroughly, including pagination semantics via nextCursor and hasMore, so the description needn't repeat them. With no output schema, naming the list return and the cursor follow-through is sufficient coverage.

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% across all 9 parameters, including the enum meanings for sort and order and the memberId example value. The description's only parameter claim, 'Requires memberId,' restates the schema's required list without adding meaning, so the baseline of 3 is appropriate.

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 comments a Stack Overflow user has written,' with the sort axis named. An agent can distinguish it from post-comment siblings by the 'user has written' scoping, though no sibling is named 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?

The prerequisite ('Requires memberId') is stated, and the sort options are named, but there is no explicit when-to-use guidance, no exclusions, and no pointer to the alternative tool for post-level comments. Usage is implied rather than directed.

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